cesnimda
51 lines
4.5 KiB
Markdown
51 lines
4.5 KiB
Markdown
# Jobjakt Redesign Documentation
|
|
|
|
This folder defines the product and UX direction for the full redesign of Jobjakt.
|
|
|
|
The redesign is not a visual reskin. It is a controlled restructuring of the product into a modern, professional, supportive career SaaS aimed at the Norwegian job market while preserving existing functionality.
|
|
|
|
## Core product idea
|
|
|
|
Jobjakt should become a personal career dashboard that helps a user move through the full job-search journey:
|
|
|
|
1. Find or import a job.
|
|
2. Analyse the role.
|
|
3. Compare it with the user's Career Profile.
|
|
4. Choose or tailor a CV.
|
|
5. Create or tailor an application/cover letter.
|
|
6. Apply.
|
|
7. Track progress, tasks, deadlines and events.
|
|
8. Prepare for interviews.
|
|
9. Record outcomes.
|
|
10. Learn from job-search analytics.
|
|
|
|
AI should support this flow naturally and contextually. It must never invent facts about the user.
|
|
|
|
## Documents
|
|
|
|
- [PRODUCT_VISION.md](PRODUCT_VISION.md) — product positioning, principles, users and success criteria.
|
|
- [INFORMATION_ARCHITECTURE.md](INFORMATION_ARCHITECTURE.md) — proposed navigation and page hierarchy.
|
|
- [UX_FLOWS.md](UX_FLOWS.md) — core user journeys and interaction patterns.
|
|
- [DASHBOARDS.md](DASHBOARDS.md) — personal and admin dashboard requirements.
|
|
- [DESIGN_SYSTEM.md](DESIGN_SYSTEM.md) — visual direction, layout, components and motion.
|
|
- [AI_PRINCIPLES.md](AI_PRINCIPLES.md) — non-negotiable AI behaviour and UX rules.
|
|
- [RESPONSIVE_ACCESSIBILITY.md](RESPONSIVE_ACCESSIBILITY.md) — mobile, responsive and accessibility requirements.
|
|
- [FUNCTIONAL_GUARDRAILS.md](FUNCTIONAL_GUARDRAILS.md) — rules for preserving existing behaviour during the redesign.
|
|
- [IMPLEMENTATION_PLAN.md](IMPLEMENTATION_PLAN.md) — phased redesign and migration strategy.
|
|
- [ASTRA_HANDOFF.md](ASTRA_HANDOFF.md) — instructions for the coding agent that will eventually execute the redesign.
|
|
- [OPEN_DECISIONS.md](OPEN_DECISIONS.md) — deliberately unresolved product decisions.
|
|
|
|
## Status
|
|
|
|
2026-09-13: [Phase 5 documentation-only plan](phase-5/README.md), based on `2a2f9e4`, reconciles P4-06's conditional planning verdict, all 57 contracts and 31 existing routes. P5-00 shell readiness is required before P5-01's first major visible redesign. Board query parity, native package preservation and CV revision/rendering have separate dependent gates. No Phase 5 implementation or B07; F04 remains open. Earlier entries below describe their historical checkpoints.
|
|
|
|
2026-09-11: [P4-01 semantic color/focus checkpoint](phase-4/p4-01/README.md), based on `f696f23`, implements the bounded shared MUI foundation and loaded-state regression fixtures. Final 916 backend / 333 frontend pass; browser 35 actual passes + the unchanged expected failure. [Preservation and visual evidence](phase-4/p4-01/TRACEABILITY.md) records both themes and intentional gaps. [Phase 4 checkpoints](phase-4/README.md) track the follow-up. P4-02, broader layout/route redesign and B07 remain unstarted; F04 remains open. Earlier status entries below are historical.
|
|
|
|
2026-09-10: [Phase 3 UX architecture checkpoint](phase-3/README.md), based on Phase 2 `d6d3dd9`, defines grouped navigation, all 31 route destinations, 57 PRES impacts, workflow/data boundaries and the bounded Phase 4 foundation plan. Documentation only; no visual implementation or B07. F04 remains open. [Phase 2](phase-2/README.md) retains the executed 916 backend / 313 frontend baseline and explicit browser/provider/production gaps. Earlier status entries below are historical.
|
|
|
|
These documents define the intended target state. They should be updated as the remaining functional work is completed. The full redesign implementation should begin only after a stable pre-redesign baseline has been created and protected by tests.
|
|
|
|
2026-09-09: [Phase 1 source audit](audit/README.md) completed on `codex/ui-redesign-audit`: current routes, protected functionality, component/test/API inventories, identity/storage boundaries and proposed migration gates. No redesign implementation or B07 started. Required release checks and F04 production verification remain separate from this audit's completion.
|
|
|
|
2026-09-10: [Final Phase 1 summary and scope classification](audit/PHASE1_SUMMARY.md) completes the audit checkpoint: 57 protected capability groups, 31 route patterns, existing-versus-new distinctions, preservation contract, baseline defects/tests and the recommended Phase 2 baseline session. This finalization changes documentation only. B06/F04 runtime and production closure remain open; no Phase 2+ work has started.
|