Specify cards for the reference quadrant's landing page - #327
Merged
Merged
Conversation
narrative spec §3.9 kept the reference quadrant out of the landing-page shape on 2026-09-11, on two premises. The second, that its introduction named two of its six pages rather than enumerating them, was false when written: the opening paragraph had listed all six since #210, and #322 extended that list by hand to seven. The first, that its entries are reached by name, is answered by a card rather than contradicted by one. §3.9 now records the correction and specifies the card shape: a 1 2 2 2 grid with the API card leading, icons in the root page's vocabulary with a dark halo matched to the measured ground, and the same four gate checks under CARD_SECTIONS. It also corrects the gate paragraph, which said the gate discovers the quadrant directories; it lists them. §7's item is Refined, and §4 and §5 record the companion changes. Four other specifications carried the old decision and are updated with it: whatsnew spec §4, contributor spec §7, start spec §6, and tour spec, whose "No landing table, still" has been stale since #306. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C79QePZ862i61EJodupwVT
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C79QePZ862i61EJodupwVT
Documentation build overview
15 files changed ·
|
This was referenced Sep 15, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Amends
narrative spec §3.9so the reference quadrant's landing page takes a grid of cards, and brings four other specifications into line. Specification only — the plan and the build follow as their own pull requests, as the landing tables (#274/#275/#276) and What's New (#319/#320/#322) did.Why the 2026-09-11 decision is reversed
It kept the reference quadrant out on two premises.
git showrather than recalled.§3.9 keeps the 2026-09-11 amendment as the record and adds a dated correction beneath it.
The shape, and what measured it
.. grid:: 1 2 2 2, the API card leading at full width. Rendered in Chromium at 360, 600 and 1280px against three alternatives. Two columns at every breakpoint — the root page's.. grid:: 2— broke words mid-word at 360px ("Configuratio / n"); three columns squeezed each sentence to four lines; seven cards in two columns leave an odd one out.#14181e, the ground measured behind a card. The root page's#20242bleaves a visible ring there, so its dark Tutorials icon is corrected with them.tippy_skip_anchor_classeskeepssd-stretched-link; the tip is generated and never attached. So the table rule "a row's sentence is not the page's opening, because a hover shows it" does not carry over to cards — which I first got wrong by reading the generated payload, exactly the traptooltip spec §3.3records.CARD_SECTIONSbesideTABLE_SECTIONS, the same four checks, and the API entry — which exists only while a build runs — derived by executingconf.py, astests/test_docs_whatsnew.pydoes.Also corrected in §3.9
The gate paragraph said
tests/test_docs_landing_pages.pydiscovers the quadrant directories rather than listing them. It lists them, in constants, and discovers the pages.Carried into four other specifications
whatsnew spec §4contributor spec §7start spec §6tour specdeveloper/The last is not about the reference quadrant; it is the same decision thread, stale since #306, and included at Bill's request.
Verification
On
b47b843:tests/test_citations.py,tests/test_github_references.pyandtests/test_docs_landing_pages.py— 80 passed; a fail-on-warning docs build,check_rendered_citations.pyandcheck_documentation_links.pyall pass; every hook passes on the five changed specifications. The fragment,1c72a6a, passed the hooks at commit and renders intowncrier build --draftunder Documentation.🤖 Generated with Claude Code
https://claude.ai/code/session_01C79QePZ862i61EJodupwVT