The older look. Here for comparison, not for approval — the new look is the venue page, Paradesi Synagogue.
cats of Kochi

Foot of a 2,000-word memoir

…and four days before the church opened, he was dead. They finished the ceiling without him.

Index · everywhere we have written about

Places

Every building, café and stretch of water we have written about, and what we think of it.

Fort Kochi

Mattancherry

⭐ The Guardian's answer, measured — and it is a negative one

I checked the foot of a current review for their onward routes. It has zero rich-links, no "related content", no "more on this story". The only onward offer is "Most viewed" — popularity, not relevance — plus the section navigation.

So Guardian-faithful means: no related-posts grid. Which confirms the instinct — it is the shape everyone reaches for and they, of all people, do not use it.

⚠️ But their reason does not transfer. Their reader arrives with a masthead, twelve section fronts and a habit. Yours arrives sideways from Google, onto one deep page, having never seen the rest of the site — and the footer offers nothing. Named reader difference: a slow guide, not a news product — fewer entry points.

So we need an onward route where they need none. It is just not a grid.

What to offer after a memoir, and how the page knows

⭐ The site has an axis a news site does not: every piece is about somewhere. So the onward block is ordered by how likely it is to be useful to a person who may be standing outside the building they just read about:

  1. The place itself. One link, amber, above everything — because it is where the hours live. The memoir tells you why the church matters; the venue page tells you whether you can get in. The page knows because the piece is tagged to a venue, not to a subject.
  2. What else is a few minutes' walk away. Geographic, not topical. ⭐ Someone who just read about Santa Cruz is far better served by "St Francis is 200 metres away" than by "other churches we have covered".
  3. More from the same cat. A lens, not a category — readers follow writers, and this list assembles itself from the byline with no upkeep.

⛔ Not offered: "related posts by tag". Tags are subjects, and subject similarity is the weakest of the three signals for a reader who is physically somewhere.

The place index is the browse surface, and it earns its keep twice

⭐ One lassi shop appears in nine files with five different descriptions. The place index is where that stops: the venue page is where the fact lives, and the index is how anyone reaches it. Note the row reading "appears in 9 pieces" — that count is not a vanity metric, it is the argument.

It also gives the 53 tag redirects an honest destination — about 30 of those tags are venues, and a venue row is a real target rather than a generic archive.

Reused, not invented

⭐ The index row is the same component as the told-page listing row — kind, name, verdict, optional count, Map. No new component was needed for this page type, which is the sign the earlier one was cut at the right joint. It still works with no verdict, as Kashi Art Café shows.

⚠️ Now carries <meta charset="utf-8"> — the middots and em-dashes above would otherwise render as mojibake, as they did across the first eight kits.

⚠️ Rendered in Figtree, the real face — inlined as base64 below, it downloads inside an artifact the same as anywhere else.