TemaDeveloper / TemaDeveloper/personal_planner
feat(dashboard): Salience-driven dashboard ordering & hero selection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Size: M.
orderBySalience() exists in src/lib/profile/reconcile.ts but the dashboard still hardcodes hero/metric selection (src/components/dashboard/dashboard-cards.tsx:~90, "prefer week earnings if work enabled, else gym, else null").
Scope
Wire section/KPI ordering and hero-metric choice to each section's driving-facet salience so the dashboard reshapes per person. Delivers the "salience-driven dashboard" from the adaptive M0 spec (§2.3/§5).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with orderBySalience() in src/lib/profile/reconcile.ts, then inspect the hardcoded hero and metric selection around line 90 of src/components/dashboard/dashboard-cards.tsx and the adaptive M0 spec sections 2.3 and 5. Done means dashboard sections and KPIs are ordered by each section’s driving-facet salience, with hero selection adapting per person.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100