Navigation IA / route cleanup¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In progress |
| Estimate | 1w (M) |
| Confidence | Medium |
| Linear | PIN-78 ↗ PIN-81 ↗ |
| Linear status | Done |
| Cycle | C14 |
| Design | Design ↗ |
| Linear epic | Platform Foundation |
| Module | Settings & Admin ↗ |
Priority: Low
Scope¶
Canonical navigation IA locked across desktop and mobile, with legacy/duplicate shell components and routes cleaned up so only one intended entry point remains per product area. (Source: PIN-78, PIN-81.)
Acceptance criteria¶
- Desktop and mobile navigation trees explicitly defined, with one primary entry point per product area
- Duplicate labels and overlapping destinations reconciled
- Inactive shell components and duplicate/legacy routes removed or clearly marked non-authoritative
- Route naming made consistent across settings and related modules
- Hover-only, mobile-only, and fullscreen navigation affordances validated in-browser
- Docs, diagrams, and app-map naming made consistent with the shipped nav
Conor's comments¶
Theirs is a lot more in setting & admin now
Notes¶
Legacy shell removal (epic-12); 25 destinations ratified
Open question for Conor¶
-