cesnimda
94 lines
2.3 KiB
Markdown
94 lines
2.3 KiB
Markdown
# Open Decisions
|
|
|
|
These items are intentionally not locked yet.
|
|
|
|
## 1. Product name
|
|
|
|
Current name: Jobjakt.
|
|
|
|
Desired direction:
|
|
|
|
- Norwegian or Scandinavian identity,
|
|
- professional,
|
|
- supportive,
|
|
- suitable for a commercial SaaS,
|
|
- capable of representing more than job tracking alone.
|
|
|
|
Potential naming direction:
|
|
|
|
- Norwegian-first name,
|
|
- Scandinavian-sounding name that is internationally usable.
|
|
|
|
Do not rename the product during the redesign without an explicit decision.
|
|
|
|
## 2. Logo
|
|
|
|
A new logo is required.
|
|
|
|
Requirements:
|
|
|
|
- works as wordmark and compact icon,
|
|
- works in light/dark modes,
|
|
- professional rather than playful,
|
|
- not a generic AI sparkle mark.
|
|
|
|
## 3. Primary brand colour
|
|
|
|
One primary brand colour should anchor the UI.
|
|
|
|
Exact colour is not yet chosen.
|
|
|
|
## 4. Default language
|
|
|
|
English and Norwegian should remain first-class.
|
|
|
|
The exact default language behaviour should be confirmed before final launch if the current application does not already define it.
|
|
|
|
## 5. Email delivery service
|
|
|
|
Required capability:
|
|
|
|
- secure transactional email from the application/server,
|
|
- notification emails,
|
|
- account/verification emails where applicable.
|
|
|
|
Provider and infrastructure choice should be made separately based on security, deliverability, cost and operational requirements.
|
|
|
|
Do not build an ad-hoc unauthenticated SMTP relay.
|
|
|
|
## 6. Calendar integration
|
|
|
|
Desired future direction:
|
|
|
|
Allow job-related events such as interviews, deadlines and follow-ups to connect to calendar events.
|
|
|
|
The initial redesign should model events cleanly enough that calendar integration can be added later.
|
|
|
|
## 7. Job-goal defaults
|
|
|
|
Weekly goals should be optional and supportive.
|
|
|
|
Do not hard-code a universal "correct" number of applications per week without a separate product decision.
|
|
|
|
## 8. Job quick preview
|
|
|
|
Preferred direction:
|
|
|
|
- full dedicated Job Detail page,
|
|
- optional quick-preview drawer from Jobs.
|
|
|
|
The preview drawer should only be implemented if it improves scanning without duplicating excessive UI.
|
|
|
|
## 9. Frontend component/styling stack
|
|
|
|
The coding agent should first identify the current stack.
|
|
|
|
It may recommend replacing or standardising the UI layer, but the choice should be justified by:
|
|
|
|
- maintainability,
|
|
- accessibility,
|
|
- consistency,
|
|
- migration cost,
|
|
- bundle/runtime impact,
|
|
- developer ergonomics.
|