[UX] Implement the chosen design #366

New issue

Open

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

claude-bot commented

2026-08-25 20:39:27 +00:00

Contributor

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. Suggested order, highest-value first: dashboard and navigation, then session, then prep, then at-the-table, then wiki and lore review, then the remainder.

Dependency: v4.3.0 lands first. That milestone fixes the structural problems — missing links, wrong destinations, silent failures, absent acknowledgement, the missing web RSVP, the attention surface. Rebuilding the visual layer over broken plumbing would bake the problems in and make them harder to see.

Ordering note: the naming decisions from the brief should land early, because renaming is cheapest before the new surfaces exist and most disruptive afterwards.

Acceptance criteria

Every surface rebuilt on the design system
All six core journeys pass on desktop and phone
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

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. Suggested order, highest-value first: dashboard and navigation, then session, then prep, then at-the-table, then wiki and lore review, then the remainder. **Dependency:** v4.3.0 lands first. That milestone fixes the structural problems — missing links, wrong destinations, silent failures, absent acknowledgement, the missing web RSVP, the attention surface. Rebuilding the visual layer over broken plumbing would bake the problems in and make them harder to see. Ordering note: the naming decisions from the brief should land early, because renaming is cheapest before the new surfaces exist and most disruptive afterwards. ## Acceptance criteria - [ ] Every surface rebuilt on the design system - [ ] All six core journeys pass on desktop and phone - [ ] 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

claude-bot added this to the v4.4.0 - UX Overhaul: Design Exploration & Rebuild milestone

2026-08-25 20:39:27 +00:00

claude-bot added the

enhancement

frontend

labels

2026-08-25 20:39:27 +00:00

claude-bot referenced this issue

2026-09-06 19:30:20 +00:00

v4.4.0 build order: UX Overhaul in six phases, with two review checkpoints #535

claude-bot referenced this issue

2026-09-11 00:02:30 +00:00