cesnimda
4.6 KiB
Information architecture
Affected: all 57 PRES contracts; per-group destinations. Recommendation ARC-01.
Navigation tree
Use understandable labels with EN/Bokmål translations; English below specifies meaning, not final translation strings.
| Primary group | Primary destination | Secondary navigation / contextual entries |
|---|---|---|
| Home | Dashboard | Customize; links to Analytics, due follow-ups and source jobs |
| Job search | Jobs | Tracked jobs (Table / Board), Discover, Follow-ups, Companies, Offers; Trash in workspace utilities |
| Job search | Correspondence | Inbox, Drafts, Review; linked job and connected-provider entry |
| Career | Career Profile | Overview, Edit, Import review/history, Evidence |
| Career | CVs | Library/templates; selected CV editor |
| Career | Documents | All supported artifacts; type/job/state filters; links to CV library and job editors |
| Insights | Analytics | Overview, trends, breakdowns, stage/salary insights; source-job filters |
| Account | Settings | Account, Security, Appearance/language, Notifications/rules, Connections, AI/plan, Data/privacy |
| Admin, authorized only | Admin dashboard | Aggregate product overview (new); Users, Audit, System as distinct secondary pages |
Correspondence earns a primary entry because it has independent inbox, drafts, provider review and real-send workflows (PRES-M01–M06). Hiding it in Documents would blur messages and files. The Jobs secondary navigation keeps discovery, follow-ups, companies and offers visible without separate duplicate top-level menus. A direct child URL selects Jobs as its primary parent even when the path is not prefixed /jobs.
Notifications remain globally reachable through the bell; an expanded centre can have a utility route. Background operations remain reachable from the centre and Settings/System activity link for the user. Admin operations remain separate from the user's operations. No empty Admin dashboard is shipped before its aggregation exists.
Page and workspace hierarchy
- Dashboard answers “what needs attention?” Analytics answers “what happened, over which period and sample?” A metric deep-links to its source/filter, not a second unrelated dataset.
- Jobs is the work index. Table/Board is presentation, not pipeline identity. Discover is a separate search source within Jobs; importing still requires review.
- Job workspace owns ongoing work on one job: Overview, Match, Application, Documents, Timeline, Notes & tasks, Interview. Correspondence is contextual within that job and also accessible through the inbox.
- Career Profile owns canonical facts. CVs selects/renders those facts with document overrides. Documents helps find the resulting resources without creating a second CV database/editor.
- Account means login identity, sessions, privacy and preferences. “Career Profile” never means login/email settings.
- Admin has privileged aggregate/operational work; personal Dashboard always remains personal, even for an administrator.
Secondary navigation rules
Keep a stable Jobs workspace navigation row on list/discovery/company/offer/follow-up surfaces. On /jobs/:id use Jobs breadcrumb/back plus document-specific tabs; do not stack both full navigation rows and seven more tabs on a phone. Secondary items live in a labelled select on narrow layouts when they cannot fit.
Use a simple Settings section list with links to existing /profile and /settings/connected-accounts until their content is safely relocated. Their primary owner is Settings; there are no duplicate Account/Profile menu destinations. Existing tab content, import/export, capture setup, billing availability and deletion controls remain reachable.
Avoid a separate “AI” route. Contextual AI actions open relevant review/assistant surfaces. Avoid top-level Cover letters, Applications, Board or Templates entries when the existing workspaces already own them.
Classification and sequencing
Grouped navigation and Jobs consolidation are UX improvements to existing behavior. Analytics and Documents are new destinations, built from existing functions plus explicitly qualified read requirements. Global cross-job document search and product/admin aggregation are new API work when no suitable endpoint exists. Dashboard customization is Phase 8 work, not a prerequisite to naming its destination.
No capability is deprecated. MUI/Emotion and existing route/data owners remain. Route plan is the authoritative migration table; Component architecture identifies reuse. Navigation simplification must not remove advanced, provider, privileged or low-frequency functionality.