Repository navigation
Conversation
…he docs map (#143) how-it-works/ (content adapter, kind help) explains levels, stages, cells and the cart in one screen; every paragraph ends with a docs map link. The header Help link, the landing card and the legend open it. Stage and level pages get an explanatory lead with the data description below it; the five legend markers carry a title and show it on hover and focus without JavaScript; section headings of the stage, level, rule and setup pages get a "?" link (partials/help-link.html) whose target comes from rulebook.json. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…nd alcops.dev as a forbidden site literal (#143) The fixture builds 40 pages and the shipped template 638 (#124 pin: stages + levels + rules + 3); the Hugo stand-in writes how-it-works/index.html. The real-Hugo case checks the help page, its four docs map links, the header Help link, the legend tooltips and that every help link starts with a docs map value whose section exists on the template page. The Deploy test forbids an alcops.dev literal in site files; CI checks the help page of the publish run. Template file counts: 99 files, 33 under site/. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…what shipped; the help on the user page; release note (#143) docs/dashboard.md gains the WP16 goal and site constraints (section 1), the decisions of the WP16 interviews (section 2), why the site carries no documentation (section 3, D58), the help bullet, the how-it-works and help link views, the page kinds and leads, and a subsection that lifts the design notes of #136 and its children with one line per deviation. The user page lists how-it-works/, the tooltips and the help links. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…its heading text, how-it-works/ in the reachability check (#143) The legend markers carry the explanation as aria-label and no title (no second tooltip, a full accessible name); site.css shows attr(aria-label). The stage summary section is labelled by a span around the heading text, so the help link is not part of its name. how-it-works/ wording: a stage can adjust the level result, the cart opens a prefilled issue form. Publish requests how-it-works/ too (37 URLs in the shipped set); docs follow. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Closed
4 tasks
This was referenced Oct 29, 2026
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.
Closes #143. Last child of WP16 (#136).
What
how-it-works/(content adapter +layouts/how-it-works/single.html,main.page-help): one screen on levels, stages, cells and their markers, and the cart. Each paragraph ends with a link from thedocsmap ofrulebook.json(levels,alProject,dashboard,changingARule); the markers also linkoverrides,twinsandquarantine. The header Help link, the landing card "How this works" and the legend open it. Publish requests it in the reachability check (37 URLs in the shipped set).p.intro).span.tip[role=img]whosearia-labelis the explanation;site.cssshows it on hover and on keyboard focus without JavaScript.partials/help-link.htmlwrites a?(a.help-link,aria-label="Help: <topic>") after the section headings of the stage, level, rule and setup pages, with thehrefof adocskey and an optional heading id; no site file names a URL.alcops.devjoins the forbidden literals oftemplate/site/.stages + levels + rules + 3); the Hugo stand-in, the Publish.Action tests and the CIpublish-actionchecks follow; template files 99,site/33.docs/dashboard.mdsections 1 to 4 finished for WP16, with the design notes of WP16: Site redesign #136 and its children and one line per deviation;template/docs/dashboard.mdsection 1 lists the page, the tooltips and the help links; release note.Tests
node --test tests/site/: 35 passed (unchanged).title, the stage summary named by its heading text, the page without JavaScript, no foreign request, no page error. Screenshots: WP16: in-context help (How this works page, leads, legend tooltips, deep links to alcops.dev) #143 (comment)Deviations
Listed in the comment on #143:
docsmap came with WP16: design system and app shell (tokens, logo, header, dark mode, mobile, sticky matrix, favicon, Open Graph, footer) #138; it targets the template pages on GitHub until Docs handover to alcops.dev: serve template/docs/ from the site #105 (D58).docsUrlis no longer read by any site file.Review
Sonnet code-review round 1 found no must-fix. The should-fix items and the nits are applied in 0b337a5:
aria-label, with notitle.how-it-works/is in the reachability manifest (36 → 37 URLs).🤖 Generated with Claude Code