What happened here

Nothing written since Tuesday

The clubs still run every afternoon, 2–6 PM. See the week.

⛔⛔ 1. Photo-less entries are out of VIEW, not out of existence

The owner has ruled the mockups pull only photo-bearing entries for now, and his team is adding the missing photographs — so a missing photo is a transient state. ⭐ 121 of 214 carry one, so there is plenty of real material.

⛔ But some entries will never have one. 1 August — the room closed for heavy rain; nobody photographs a shut room. 2 August — the dance group meeting; simply was not. ⭐ So the case does not disappear. It stops being 36% and becomes rare.

⛔⛔ The no-photo form stays in _kit.css and stays documented. The failure to guard against is somebody later reading “we never see this” as “this cannot happen” — which is how empty-state work gets deleted as dead code and then rediscovered by a reader.

⭐ 2. The grid got a fair test at last

It was rejected earlier on evidence gathered while the aspect-ratio bug was live — photo cards 1300px against 88px, a 15× spread. ⛔ Nobody re-tested it after the fix, and post-fix the spread was 3×. ⚠️ With photo-less entries now out of view the objection is suspended entirely, so this is the layout he asked for twice, on its own merits.

⭐⭐ 3. The type hierarchy, measured on the page he linked

Airbnb's listing card carries exactly three treatments: title 15/500 #222222, secondary 15/400 #6C6C6C, price 15/500 #222222. ⭐⭐ One type size. Two weights. Two colours. They do not vary size at all — and three consecutive lines share one treatment.

⛔ Our card was flat because of one line: .act__body was 20px at #262626 — the same colour as the headline and only 3px smaller, so the excerpt competed with it. It now takes the secondary treatment and shares it with the date. ⛔ And no second anchor was invented — a listing has a price; an activity has no equivalent.

⚠️ One honest deviation: we vary size (23 vs 16) where Airbnb does not (15 vs 15). Defensible — ours is a real headline, not a card title over a photograph — but it is a departure and worth naming.

⛔ 4. No border, and his own second screenshot is the argument

Measured on the page he linked: the listing card is border: 0px none, background: transparent, box-shadow: none, radius 20px. The review block on the same page: border 0, radius 0, transparent, no shadow.

⭐ The bordered element in his first screenshot is the reserve panel — a form you act inside, not a content card. ⛔ “Airbnb does it” was true and about the wrong element. Three treatments, three jobs, one product.

⛔⛔ 5. Every July and August weekday on this page was WRONG, and it was mine

Checked against the real 2026 calendar: 7 August is a Friday, not a Thursday. 6 August is a Thursday. 4 August is a Tuesday. 4 July is a Saturday, not a Friday. Five of the eight dates on this page named the wrong day of the week. All are corrected above.

⚠️ And it was not a uniform off-by-one, which is why it survived. The three May dates were right. A consistent slip is visible; a slip in one stretch of a list looks like data. ⛔ Nothing on the page could have caught it — every weekday name is a valid string, correctly styled, in the right place.

⛔⛔ This is the worst defect found today, and it is not a layout defect. The whole claim of this page is this happened, on this day. A record that names the wrong weekday is not a smaller version of the truth, it is a different statement. ⭐ Someone who was in the room on Saturday reads “Friday” and stops believing the rest.

⭐⭐ For the importer: derive the weekday from the date, never transcribe it. The source guides carry “July 4” with no weekday at all, so every weekday on this site will be computed. Compute it once, in one place, and the whole class of error disappears. ⚠️ Fix the timezone at Asia/Kolkata when you do — a date rendered in UTC lands on the previous evening and shifts the weekday back by one, which is exactly the error above, mechanised.