# Information Architecture

## Navigation model

Use a collapsible left sidebar as the primary desktop navigation.

Navigation should be grouped into meaningful sections rather than presented as one flat list.

Recommended structure:

## Home

- Dashboard

## Job Search

- Jobs
- Analytics

`Jobs` should contain both table/list and Kanban/board views using a view switch. Kanban should not be a separate top-level navigation destination.

## Career

- Career Profile
- CVs
- Documents
- Applications / Cover Letters if still required as a distinct workflow

Where possible, document-related features should converge under a clearer `Documents` area rather than creating many disconnected top-level pages.

## Account

- Notifications
- Settings

## Admin

Visible only to authorised administrators.

- Admin Dashboard
- Users / support tools if required
- Product analytics / operational controls if required

## Global interaction areas

The application shell should include:

- global search / command palette,
- notifications,
- user/account menu,
- language control,
- appearance/theme control where appropriate,
- contextual AI entry point.

## Command palette

Provide a global `Ctrl+K` / `Cmd+K` command palette.

It should be able to:

- search jobs,
- search companies,
- search CVs,
- search documents,
- navigate to pages,
- create a job,
- create a CV,
- open Career Profile,
- toggle appearance,
- change language,
- invoke context-relevant commands.

## Page hierarchy

### Dashboard

Personal overview of the user's job search, goals, tasks, deadlines, activity and analytics.

### Jobs

Single consolidated workspace with:

- Table view
- Board/Kanban view
- Search
- Filters
- Saved view preferences
- Add/import job

Desktop default: table.

Mobile default: card/list representation.

### Job Detail

Use a dedicated page for full job detail.

Recommended top-level structure:

- Overview
- Match
- Application
- Documents
- Timeline
- Notes / Tasks

Exact grouping may change during UX implementation, but all information should feel like parts of one job workspace rather than unrelated pages.

Optional enhancement: a quick-preview side drawer from the Jobs page with a clear action to open the full job page.

### Career Profile

The canonical user career dataset.

Suggested sections:

- Personal information
- Professional summary
- Work history
- Education
- Skills
- Technologies
- Languages
- Certifications
- Projects
- Achievements
- Preferences
- Desired roles
- Location preferences
- Remote preferences
- Salary expectations where applicable

### CVs

Library of CV variants generated from the Career Profile.

CV-specific content overrides must not silently modify the master Career Profile.

### Documents

Unified document workspace containing, where applicable:

- CVs
- Cover letters
- Application answers
- References
- Certificates
- Other attachments

Documents should show relationships to jobs where relevant, e.g. "Used for Kongsberg — Software Developer".

### Analytics

Deeper job-search analytics beyond the dashboard.

### Notifications

In-app notification centre with links back to relevant jobs, tasks, deadlines, interviews and documents.

### Settings

Suggested sections:

- Account
- Profile preferences
- Language
- Appearance
- Dashboard preferences
- Notification preferences
- Email preferences
- Privacy / data
- Subscription / billing if applicable

## Avoid unnecessary top-level pages

The redesign should actively identify pages that can be merged into coherent workspaces.

A feature should not receive a top-level route merely because it currently has one.