Missing back navigation on detail pages (audit + shared affordance) #6

New Issue

2026-07-03T23:55:34-05:00

ginnoir commented

2026-07-03 23:55:34 -05:00

Audit detail routes lacking back affordances; add a shared header/back pattern.

Background / current behavior

Individual plant pages (and other detail routes) have no in-page "back" except global nav. Affects many detail pages under src/app/.

Expected behavior

Every detail page has a consistent back control to its parent list/index. Prefer a shared header/back component.

Acceptance criteria

Audit all routes in src/app/ and list detail pages missing back in the PR description.
Shared back affordance applied consistently.
Playwright: tests/e2e/navigation.spec.ts or per-module — open plant/note/list (and other) detail routes → Back visible and returns to parent.

Priority

P1 (batch step 5). Task brief: docs/tasks/84-back-navigation.md.

<brief>Audit detail routes lacking back affordances; add a shared header/back pattern.</brief> ## Background / current behavior Individual plant pages (and other detail routes) have no in-page "back" except global nav. Affects many detail pages under `src/app/`. ## Expected behavior Every detail page has a consistent back control to its parent list/index. Prefer a shared header/back component. ## Acceptance criteria - [ ] Audit all routes in `src/app/` and list detail pages missing back in the PR description. - [ ] Shared back affordance applied consistently. - [ ] Playwright: `tests/e2e/navigation.spec.ts` or per-module — open plant/note/list (and other) detail routes → Back visible and returns to parent. ## Priority P1 (batch step 5). Task brief: `docs/tasks/84-back-navigation.md`.

ginnoir added the bug priority/p1 labels 2026-07-03 23:55:34 -05:00

ginnoir closed this issue

2026-07-04 22:03:08 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ginnoir/famapp#6