[UX] Implement the chosen design #366

Closed
opened 2026-08-25 20:39:27 +00:00 by claude-bot · 5 comments
Collaborator

Found in the August 2026 session lifecycle review (#319). The build-out, once a direction is selected.

Scope

Implement the agreed design across every surface, on the component library, in a sequence that keeps the product usable throughout. The design is settled: the brief (docs/design/v4.5.0-brief.md, D1 to D85), the catalogue (1,706 rows on 107 surfaces), the prototype (every surface drawn and reviewed, #659) and the coverage scripts (one per lane). The sequence and the engineering rules are the build plan, docs/design/v4.5.0-build-plan.md: page by page inside the new shell, no feature flags, main deployable after every PR, the dev server as the staging.

Dependency met: v4.3.0 (the structural fixes) closed on 2026-09-12.

The naming decisions from the brief land in lane 1, because renaming is cheapest before the new surfaces exist.

The lanes, in order

  • Lane 0 — the design system and component library (#364)
  • The journeys harness, introduced with lane 1 (#726)
  • Lane 1 — the shell, Home and you (#727)
  • Lane 2 — the public pages (#728)
  • Lane 3 — the campaign core and Settings (#729)
  • Lane 4 — sessions (#730)
  • Lane 5 — the table (#731)
  • Lane 6 — Prep and Planning (#732)
  • Lane 7 — talking (#733)
  • Lane 8 — the wiki (#734)
  • Lane 9 — Admin (#735)
  • Lane 10 — outside the app (#736)
  • Lane 11 — stat blocks and character sheets (#737); may run beside 9 and 10 once 8 has landed
  • The accessibility pass at the end (#367)

Acceptance criteria

  • Every surface rebuilt on the design system; each lane's coverage script rows built
  • All seven core journeys pass on desktop, on a phone and keyboard-only, in the journeys suite
  • The behaviours listed as "must survive" in the brief are intact
  • One vocabulary throughout, matching the brief
  • No page-level error handling that destroys rendered content
  • Every async operation shows progress and a failure next-action
  • The product remains usable at every step of the rollout
  • From #365, folded in here: every surface reachable at 375 px, verified on a real device; touch targets meet the design system's 44 px minimum; the at-the-table journey (J4) completes on a phone end to end
Found in the August 2026 session lifecycle review (#319). The build-out, once a direction is selected. ## Scope Implement the agreed design across every surface, on the component library, in a sequence that keeps the product usable throughout. The design is settled: the brief (`docs/design/v4.5.0-brief.md`, D1 to D85), the catalogue (1,706 rows on 107 surfaces), the prototype (every surface drawn and reviewed, #659) and the coverage scripts (one per lane). The sequence and the engineering rules are the build plan, `docs/design/v4.5.0-build-plan.md`: page by page inside the new shell, no feature flags, main deployable after every PR, the dev server as the staging. **Dependency met:** v4.3.0 (the structural fixes) closed on 2026-09-12. The naming decisions from the brief land in lane 1, because renaming is cheapest before the new surfaces exist. ## The lanes, in order - [ ] Lane 0 — the design system and component library (#364) - [ ] The journeys harness, introduced with lane 1 (#726) - [ ] Lane 1 — the shell, Home and you (#727) - [ ] Lane 2 — the public pages (#728) - [ ] Lane 3 — the campaign core and Settings (#729) - [ ] Lane 4 — sessions (#730) - [ ] Lane 5 — the table (#731) - [ ] Lane 6 — Prep and Planning (#732) - [ ] Lane 7 — talking (#733) - [ ] Lane 8 — the wiki (#734) - [ ] Lane 9 — Admin (#735) - [ ] Lane 10 — outside the app (#736) - [ ] Lane 11 — stat blocks and character sheets (#737); may run beside 9 and 10 once 8 has landed - [ ] The accessibility pass at the end (#367) ## Acceptance criteria - [ ] Every surface rebuilt on the design system; each lane's coverage script rows built - [ ] All seven core journeys pass on desktop, on a phone and keyboard-only, in the journeys suite - [ ] The behaviours listed as "must survive" in the brief are intact - [ ] One vocabulary throughout, matching the brief - [ ] No page-level error handling that destroys rendered content - [ ] Every async operation shows progress and a failure next-action - [ ] The product remains usable at every step of the rollout - [ ] From #365, folded in here: every surface reachable at 375 px, verified on a real device; touch targets meet the design system's 44 px minimum; the at-the-table journey (J4) completes on a phone end to end
Author
Collaborator

The build plan is merged (PR #738, 2026-09-22): docs/design/v4.5.0-build-plan.md. The lane checklist above links every lane's issue; the brief's §9 names them too. Five assumptions in the plan's §8 wait for the owner's confirmation (the rollout rule, the release shape, the /design page instead of Storybook, dark mode by data-mode, WCAG 2.2 AA), alongside the "agreed" on the brief (#361). After that, lane 0 (#364) can start.

**The build plan is merged (PR #738, 2026-09-22):** `docs/design/v4.5.0-build-plan.md`. The lane checklist above links every lane's issue; the brief's §9 names them too. Five assumptions in the plan's §8 wait for the owner's confirmation (the rollout rule, the release shape, the `/design` page instead of Storybook, dark mode by `data-mode`, WCAG 2.2 AA), alongside the "agreed" on the brief (#361). After that, lane 0 (#364) can start.
Author
Collaborator

Progress on the build (2026-09-22): lane 0 (#364, the design system) is built and merged in three PRs, with /design as the reference page; the journeys harness (#726) is merged and closed, with the journeys CI job green on the runner; lane 1 (#727, the shell, Home and You) is built and merged in six PRs, and stays open for the owner's review on the dev server. Main shows the new frame around every page, Home and the You pages rebuilt, and the old pages inside the frame until their lanes. Next in order: lane 2 (#728, the public pages).

Progress on the build (2026-09-22): **lane 0** (#364, the design system) is built and merged in three PRs, with `/design` as the reference page; **the journeys harness** (#726) is merged and closed, with the `journeys` CI job green on the runner; **lane 1** (#727, the shell, Home and You) is built and merged in six PRs, and stays open for the owner's review on the dev server. Main shows the new frame around every page, Home and the You pages rebuilt, and the old pages inside the frame until their lanes. Next in order: lane 2 (#728, the public pages).
Author
Collaborator

The owner's review of lanes 1–4 is complete (2026-09-25). The findings are on #727–#730.

D110 (wide screens, replacing D90). The owner compared four layouts, rendered in the real app at 2560×1440 (a 4K monitor at 150%): current, A (scale up and add columns), B (much wider text) and AB (combined). Their picks:

  • A overall, and for Home, Sessions, Read, Review, Storyline and Settings.
  • AB for This week, Help and Privacy. Licences & notices and Accessibility follow Help and Privacy.

What A means:

  • fluid type, 16px at 1440 wide to 20px at 2560;
  • a 1920px centred frame;
  • auto-fill card grids;
  • side columns at ≥1800px ("On this page", the Storyline chapters).

Phones are unchanged. Also fixed: a white band that signed-in pages paint to the right of the content.

Follow-up work:

  • R1 (fix/review-r1): the review's bugs and small decisions, D107–D109.
  • R2 (build/review-r2-wide): D110, built into the design system's tokens and the shell.
  • The demo seed (#821), so every feature can be reviewed as a player.

Lane 5 (#731) follows these, so its pages are built in the new frame.

**The owner's review of lanes 1–4 is complete (2026-09-25).** The findings are on #727–#730. **D110 (wide screens, replacing D90).** The owner compared four layouts, rendered in the real app at 2560×1440 (a 4K monitor at 150%): current, A (scale up and add columns), B (much wider text) and AB (combined). Their picks: - **A overall**, and for Home, Sessions, Read, Review, Storyline and Settings. - **AB** for This week, Help and Privacy. Licences & notices and Accessibility follow Help and Privacy. **What A means:** - fluid type, 16px at 1440 wide to 20px at 2560; - a 1920px centred frame; - auto-fill card grids; - side columns at ≥1800px ("On this page", the Storyline chapters). Phones are unchanged. Also fixed: a white band that signed-in pages paint to the right of the content. **Follow-up work:** - **R1** (`fix/review-r1`): the review's bugs and small decisions, D107–D109. - **R2** (`build/review-r2-wide`): D110, built into the design system's tokens and the shell. - **The demo seed (#821)**, so every feature can be reviewed as a player. Lane 5 (#731) follows these, so its pages are built in the new frame.
Author
Collaborator

The follow-ups from the review of lanes 1–4 are merged (2026-09-26).

  • #823 (R1): the owner's findings, D107–D109.
    • Needs you now refreshes after an answer.
    • The calendar feed has a name.
    • The Recording settings crash is fixed.
    • Read's contradictory "who was there" is gone.
    • Public pages link back home.
    • A one-shot's "when" is a date.
    • Setup closes once it's done.
    • Also fixed: two flaky tests that raced their effects under CI load, and J1 scans only the banner on Admin, which is still the legacy page (#735).
  • #825 (R2): D110, the wide-screen layout. Fluid type, a 1920px frame, auto-fill grids, side columns at ≥1800px, and a 98ch reading card with On this page for the word-heavy public pages. It also fixes the white band.

Lane 5 (#731) is under way: the decisions are in #826, three server PRs are on branches, and page PR 4a is being built in the new frame.

**The follow-ups from the review of lanes 1–4 are merged (2026-09-26).** - **#823 (R1):** the owner's findings, D107–D109. - Needs you now refreshes after an answer. - The calendar feed has a name. - The Recording settings crash is fixed. - Read's contradictory "who was there" is gone. - Public pages link back home. - A one-shot's "when" is a date. - Setup closes once it's done. - Also fixed: two flaky tests that raced their effects under CI load, and J1 scans only the banner on Admin, which is still the legacy page (#735). - **#825 (R2): D110, the wide-screen layout.** Fluid type, a 1920px frame, auto-fill grids, side columns at ≥1800px, and a 98ch reading card with On this page for the word-heavy public pages. It also fixes the white band. Lane 5 (#731) is under way: the decisions are in #826, three server PRs are on branches, and page PR 4a is being built in the new frame.
Author
Collaborator

Closing with the v4.5.0 milestone (owner, 17 Oct 2026). The redesign shipped in 4.5.0 on 12 Oct, all twelve lanes signed off. What is left of the accessibility work moves with #367 to v4.7.0.

Closing with the v4.5.0 milestone (owner, 17 Oct 2026). The redesign shipped in 4.5.0 on 12 Oct, all twelve lanes signed off. What is left of the accessibility work moves with #367 to v4.7.0.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Quest-Board#366
No description provided.