Front-end UX refresh: navigation bar, layout and contextual help #9

Closed
opened 2026-10-15 04:09:21 +00:00 by ben · 1 comment
Owner

Make the web client easier to find your way around, for every role (owner, counsellor, client).

Scope

  • Navigation bar: persistent, role-aware navigation between the existing screens (home, client dashboard, activity builder, user management, the board), replacing ad-hoc links and back buttons. It should show the signed-in account and the sign-out control.
  • Layout: spread content across the page better (grouping, spacing and visual hierarchy on home, dashboard, builder, review and the board) so each screen has a clear primary action.
  • Contextual help: a small number of ? buttons that open accessible modals explaining non-obvious concepts, for example card sorting and keyboard shortcuts, flags and notes, activity status on the dashboard, read-only review and access history, and builder archive/delete rules.

Constraints

  • Plain TypeScript, no framework (web/src); keep the fixed /cards base path, the light/dark theme toggle and the existing accessibility behaviour (focus management, keyboard use).
  • Behaviour and API unchanged: this is presentation and navigation only.
  • Keep the 85% per-file line coverage gate and the Playwright journeys green; regenerate the README screenshots.

Acceptance

  • Every screen is reachable from the nav bar for the roles allowed to see it, and hidden for the rest.
  • Help modals open from a ? control, trap focus, close on Escape, and return focus to the opener.
  • Existing e2e journeys pass with the new navigation.
Make the web client easier to find your way around, for every role (owner, counsellor, client). **Scope** - **Navigation bar:** persistent, role-aware navigation between the existing screens (home, client dashboard, activity builder, user management, the board), replacing ad-hoc links and back buttons. It should show the signed-in account and the sign-out control. - **Layout:** spread content across the page better (grouping, spacing and visual hierarchy on home, dashboard, builder, review and the board) so each screen has a clear primary action. - **Contextual help:** a small number of `?` buttons that open accessible modals explaining non-obvious concepts, for example card sorting and keyboard shortcuts, flags and notes, activity status on the dashboard, read-only review and access history, and builder archive/delete rules. **Constraints** - Plain TypeScript, no framework (`web/src`); keep the fixed `/cards` base path, the light/dark theme toggle and the existing accessibility behaviour (focus management, keyboard use). - Behaviour and API unchanged: this is presentation and navigation only. - Keep the 85% per-file line coverage gate and the Playwright journeys green; regenerate the README screenshots. **Acceptance** - Every screen is reachable from the nav bar for the roles allowed to see it, and hidden for the rest. - Help modals open from a `?` control, trap focus, close on Escape, and return focus to the opener. - Existing e2e journeys pass with the new navigation.
Author
Owner

Landed in 13541d6 and deployed (live at 13541d6, schema v5, no migration). Acceptance verified, closing.

What changed

  • App bar: a role-aware bar holds the account and the only Log out button.
    • The owner sees Sessions, Client dashboard, Activity builder, People and Outbox.
    • A counsellor sees Sessions, Client dashboard and Activity builder.
    • A client sees Sessions.
    • Pages a role can't use redirect to Sessions.
  • Pages: the old home page is split into task-focused pages, and the Client dashboard holds every client task. Wide screens use two columns.
  • Builder: the activity list sits beside a compact editor.
  • Help: seven ? buttons open help dialogs. Each dialog is modal, makes the background inert, traps focus, closes on Escape, the Close button or the backdrop, and returns focus to its button. They survive live board updates and block board shortcuts while open.
  • Navigation safeguards:
    • Unsaved builder edits ask before Back, Forward, a typed URL, a nav link or Log out.
    • Leaving a session saves its pending notes once the same account is confirmed.
    • Focus and page titles follow navigation.

Acceptance

  • Each screen is reachable from the bar for the roles allowed to see it and hidden for the rest. Tests: web/test/nav.test.ts role × route matrix, e2e web/e2e/nav.spec.ts.
  • Help dialogs open from a ? control, trap focus, close on Escape and return focus to the opener. Tests: web/test/help.test.ts, e2e web/e2e/help.spec.ts.
  • The existing e2e journeys pass with the new navigation: Playwright 8 passed, 1 skipped (screenshots only).
  • Other checks: web unit 629 tests at 98.3% line coverage, with every file at 85% or above; server 1190.
  • Review: Medium tier, two Claude worker reviewers and two delta rounds. All Medium findings were fixed.
  • README screenshots are regenerated.

Plan: docs/plans/2026-10-15-07-37_ux-nav-layout-help.md (done). Its completion notes list the accepted drift and the deferred Low items:

  • the skip link doesn't work during the builder preview;
  • Resend or Revoke on a client reached with "Load more" reloads the list from page 1;
  • some flows have unit tests but no e2e tests.

Follow-up: #10 (ADMIN_CAN_EDIT has no effect in the web client).

Landed in 13541d6 and deployed (live at 13541d6, schema v5, no migration). Acceptance verified, closing. **What changed** - **App bar:** a role-aware bar holds the account and the only Log out button. - The owner sees Sessions, Client dashboard, Activity builder, People and Outbox. - A counsellor sees Sessions, Client dashboard and Activity builder. - A client sees Sessions. - Pages a role can't use redirect to Sessions. - **Pages:** the old home page is split into task-focused pages, and the Client dashboard holds every client task. Wide screens use two columns. - **Builder:** the activity list sits beside a compact editor. - **Help:** seven `?` buttons open help dialogs. Each dialog is modal, makes the background inert, traps focus, closes on Escape, the Close button or the backdrop, and returns focus to its button. They survive live board updates and block board shortcuts while open. - **Navigation safeguards:** - Unsaved builder edits ask before Back, Forward, a typed URL, a nav link or Log out. - Leaving a session saves its pending notes once the same account is confirmed. - Focus and page titles follow navigation. **Acceptance** - Each screen is reachable from the bar for the roles allowed to see it and hidden for the rest. Tests: `web/test/nav.test.ts` role × route matrix, e2e `web/e2e/nav.spec.ts`. - Help dialogs open from a `?` control, trap focus, close on Escape and return focus to the opener. Tests: `web/test/help.test.ts`, e2e `web/e2e/help.spec.ts`. - The existing e2e journeys pass with the new navigation: Playwright 8 passed, 1 skipped (screenshots only). - Other checks: web unit 629 tests at 98.3% line coverage, with every file at 85% or above; server 1190. - Review: Medium tier, two Claude worker reviewers and two delta rounds. All Medium findings were fixed. - README screenshots are regenerated. **Plan:** `docs/plans/2026-10-15-07-37_ux-nav-layout-help.md` (done). Its completion notes list the accepted drift and the deferred Low items: - the skip link doesn't work during the builder preview; - Resend or Revoke on a client reached with "Load more" reloads the list from page 1; - some flows have unit tests but no e2e tests. **Follow-up:** #10 (`ADMIN_CAN_EDIT` has no effect in the web client).
ben closed this issue 2026-10-15 15:15:16 +00:00
Sign in to join this conversation.
No milestone
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
ben/career-values-cards#9
No description provided.