Feature: streaks and goals on the Pulse page
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 20
Description
Tier 4 — feature idea
Why
Pulse already computes completions per week, active days, completion rate and a 30-day vs previous-30 comparison — everything needed for a habit loop — but stops at reporting. Streaks and a weekly goal turn a dashboard into a reason to come back.
Evidence
LearnStack/Components/Pages/Pulse.razor.cs:88-120—activeDays,currentPeriodCompletions,previousPeriodCompletionsall already computedLearnStack/Components/Shared/PulseSignals.razor— the surface to extend
Sketch
Current and longest streak, a user-set weekly completion goal with progress, and a milestone celebration. Feed the same numbers into the weekly digest email.
Depends on
Per-user timezone — streaks computed on UTC day boundaries will be wrong for most users.
Contributor guide
No contributing guide indexed for this repository
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 LearnStack/Components/Pages/Pulse.razor.cs:88-120 to understand the existing metrics, then inspect LearnStack/Components/Shared/PulseSignals.razor. Scope the streaks, weekly goal, milestone celebration, weekly digest integration, and per-user timezone dependency; done means these behaviors use timezone-aware day boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100