Landing: give the last section a subject

[adnaan]

"Everything else / The rest of the docs covers the ordinary screens.: means nothing."

Right, and it's worse than bland — it's a heading about the documentation rather than the software. It told a reader nothing they hadn't already assumed.

Why it couldn't say anything

The section held three different taxonomies at once:

• eyebrow — "Everything else", a non-label
• heading — about the docs
• first lead — app types: admin panels, CRUD, dashboards
• eight links — capabilities: uploads, pubsub, sessions, errors, CLI, client, observability, scaling

No heading summarises three subjects, so the one there summarised none of them.

	before	after
eyebrow	Everything else	What the wall skipped
heading	The rest of the docs covers the ordinary screens.	Your app has file uploads and a login. Both are here.

The heading now names two capabilities from the grid and answers the objection a reader actually has after scrolling through a greeting wall. The lead names the rest — sessions, navigation, scaling, and what to look at when it falls over at 3am. Together they cover the eight links, which is what makes the section read as one thing.

Two links contradicted the new heading

"Shared views / Subscribe & Publish" is exactly what the Multi-user section demonstrates, and "Forms & errors" is exactly what the Validation section demonstrates. Neither is something the wall skipped.

Both references now sit at the end of the section that shows them off, where a reader who wants the API is already standing. Their grid slots go to two genuine gaps:

• Auth & login → /recipes/login/ — the old lead said "auth" and never linked it
• Navigation → /reference/navigate — nothing on the page mentioned it

One false claim, cut before it shipped

A draft of the lead promised "sessions that outlive a restart". Wrong by default — reference/session documents the SessionStore as "in-memory or Redis", and every persistence claim on that page is scoped to surviving a page refresh, not a process restart. Redis-backed behavior presented as the baseline. Same failure mode as the Alpine row in #142, one section later.

Verification

• voice-check.sh — pass, every ceiling unchanged
• tinkerdown validate — 98/98, 0 errors
• go test ./e2e/ — pass, 140s
• make sweep at desktop + iphone-14 — 196 visits, 2 flagged, both the pre-existing large-table timeout. The two new grid glosses are longer than the ones they replaced, so the two-column card grid on mobile was the risk.
• Read at 1440px in a browser
• All 10 headings still carry a finite verb; no dead in-page anchors

🤖 Generated with Claude Code

https://claude.ai/code/session_0166MK1arBYbVZq6wfm8EsQZ