Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(dashboard): Salience-driven dashboard ordering & hero selection

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

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.

Description

enhancement

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).

Dominant language
TypeScript
Stars
2
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TemaDeveloper/personal_planner

All issues in TemaDeveloper/personal_planner

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.