cesnimda
41 lines
2.0 KiB
Markdown
41 lines
2.0 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 positioning, principles, users and success criteria.
|
|
- `INFORMATION_ARCHITECTURE.md` — proposed navigation and page hierarchy.
|
|
- `UX_FLOWS.md` — core user journeys and interaction patterns.
|
|
- `DASHBOARDS.md` — personal and admin dashboard requirements.
|
|
- `DESIGN_SYSTEM.md` — visual direction, layout, components and motion.
|
|
- `AI_PRINCIPLES.md` — non-negotiable AI behaviour and UX rules.
|
|
- `RESPONSIVE_ACCESSIBILITY.md` — mobile, responsive and accessibility requirements.
|
|
- `FUNCTIONAL_GUARDRAILS.md` — rules for preserving existing behaviour during the redesign.
|
|
- `IMPLEMENTATION_PLAN.md` — phased redesign and migration strategy.
|
|
- `ASTRA_HANDOFF.md` — instructions for the coding agent that will eventually execute the redesign.
|
|
- `OPEN_DECISIONS.md` — deliberately unresolved product decisions.
|
|
|
|
## Status
|
|
|
|
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.
|