Repository navigation
[M11] Design system, page frame, hero stage and footer (M11.3) - #92
Conversation
Story M11.3. The palette, type scale and motion tokens of docs/FRONTEND_DESIGN.md become CSS custom properties in one token file, and every other stylesheet references them by name. On top of that sit the navigation, the hero (headline, one sentence, one button, the maroon stage with the three-step notch, and the live console with its boot status and tower loader) and the footer wordmark built from blocks whose heights are a real skip list's levels. web/tests/house-rules.spec.ts implements every check in section 7 at 1440, 768 and 390 wide, saves a full-page screenshot per width, walks the tab order, and runs again with the font provider blocked. A second Playwright project runs the whole suite under prefers-reduced-motion. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QWNkuNh5Bysnfo2KrxL9Sp
|
CI note, for the record. On the first run,
One limitation worth stating rather than glossing over: the Generated by Claude Code |
Builds the design system and the page frame from
docs/FRONTEND_DESIGN.md: the token file, the navigation, the hero with its shaped stage, and the block-built footer wordmark. The live console from M11.2 keeps every control and every test id it had, moved onto the stage and given the fragment's conventions, so nothing the engine already drove was lost.What changed
web/src/styles/tokens.cssis the only stylesheet with a literal colour, font family or type size: the palette (section 3), the five type steps plus the 15px chrome size that sections 5 and 6 both fix, the tower block sizes, the frame margins and the motion curves and durations (section 8).base.cssandpage.cssreference them by name.SiteNav,Hero,Console,TowerLoader,WordmarkandSiteFooterunderweb/src/components/. The stage's three-step notch is aclip-pathpolygon driven by--block-lg(72px, 40px below 1100). The footer wordmark's letter heights are a real skip list's levels, drawn with the engine's ownSkipListat the default level probability; the exact snippet that produced them is inWordmark.tsx.web/tests/house-rules.spec.tsplusweb/tests/support/house-rules.ts: every rule in section 7, at 1440, 768 and 390 wide, with a full-page screenshot per width written toweb/test-results/screenshots/, a real tab walk for keyboard reachability, Playwright's own accessible-name computation for naming, a run with the font provider blocked, and a source scan that fails on a raw colour or type size outside the token file.playwright.config.tsgains a second project,chromium-reduced-motion, which runs the whole suite underreducedMotion: 'reduce'.index.htmlloads Pilcrow Rounded from Fontshare with preconnects, without blocking the first paint, so the page renders the same when the provider is unreachable.Acceptance criteria
web/tests/house-rules.spec.tsimplements every check in section 7 at 1440, 768 and 390, passes, and passes withreducedMotion: 'reduce'.web/test-results/screenshots/. The screenshots were opened and checked against the spec (see below).What ran, and what passed
Everything ran locally, in this sandbox, and passed:
pytest: 1244 passed.ruff check src testsandruff format --check src tests: clean. No Python changed in this story; this is the pre-existing suite still green.web/:npm ci,npm run lint,npm run typecheck,npm run build: clean.npx playwright test: 26 passed, both projects. Playwright ran locally (the sandbox has a matching Chromium), not only in CI. That is 6 engine specs and 7 house-rules specs per project.The house-rules audit was negative-tested before being trusted: a temporary stylesheet with a gradient, a shadow, a monospace face, 1px borders, an 8px radius, a tracked uppercase label, a
backdrop-filter, a 12px paragraph and a low-contrast colour made all nine rules fire with the offending selector named, and the token scan caught the hex colour and the literal font size. The patch was reverted; it is not in this branch.Screenshots at 1440, 768 and 390 were opened and checked: the headline holds two lines at every width, the outer margins match on both sides and across the three bands, the notch reads as three steps, the console is fully visible and uncropped, the footer wordmark shows the varied block heights with the two tallest letters in maroon, and nothing failed to render. The web font loaded in these runs, and the blocked-font test proves the rules also hold on the
ui-roundedfallback.Decisions taken without asking
Three readings of section 6 were resolved in favour of section 7's house rules, which are the checked contract:
--step-hero, so six columns would push the headline to a third line. The headline's natural width still leaves it sitting left of the stage.Two smaller ones:
--step-herois redefined to10vwunder 600px rather than a sixth size being added for the phone headline, and the three in-page navigation links point at section ids that later M11 stories add, so the navigation does not have to be rebuilt once per story.Scope held to this story: no shutter, no section entrances, no tower or flush moves (all M11.9). The motion that is here is the boot loader, press feedback on the one button shape, hover behind
@media (hover: hover) and (pointer: fine), and the reduced-motion fallbacks, because a control with no press state is not a motion layer, it is an unfinished button.Closes #81
Generated by Claude Code