feat(onboarding): one onboarding list at a time — checklist owns activation, StartHereCard owns first five - #252
Conversation
…vation, StartHereCard owns first five A new user could see up to three competing onboarding lists at once: StartHereCard (first 5 guided actions) stacked above the employee dashboard's GettingStartedChecklist, and on the Readiness tab the 4-phase Activation Progress card stacked directly on the checklist that tracks the same milestones at finer grain. - Readiness tab: drop the Activation Progress card. Its summary numbers (milestones done, progress %) already render in the KPI bar immediately above, and the checklist is the canonical milestone list. The milestone computation stays — KPI bar and tab badge use it. - GettingStartedChecklist: retitle the generic variant from 'Getting Started / Your first wins in FormaOS' to 'Activation / Activation milestones' so it reads as the long-arc list, not a second first-steps guide. Industry variant already says Activation Roadmap. - Employee dashboard: suppress the checklist while StartHereCard is on screen (new firstSessionActive prop passed from DashboardWrapper, same pattern as the command-center prop in PR #250). No new primitives; deletes one block and removes now-unused imports.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 35 minutes and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
♿ Accessibility Test Results✅ PASSED - No critical accessibility issues found Tests Performed:
Artifacts: Download the accessibility reports from the "Artifacts" section for detailed results. |
2 participants
Summary
Surface 2 of the first-session density workstream (dashboard: #250, compliance: #251). A new user could see up to three competing onboarding lists at once. This PR differentiates them along the agreed split — StartHereCard = first 5 actions, checklist = full activation milestones — and makes sure only one is ever on screen:
StartHereCardrenders above it (newfirstSessionActiveprop fromDashboardWrapper— the same prop pattern feat(dashboard): focused first-session view — guide + live tiles only #250 introduced for CommandCenter; hunks are disjoint, so the two PRs merge cleanly in either order).Net: −83 lines, one whole block removed from the Readiness tab, and no screen ever shows two onboarding lists.
Verification
npm run typecheck— passnpx eslinton all four touched files — clean (now-unusedArrowRight/TrendingUp/DashboardSectionCard/cnimports removed)npx jest tests/dashboard/dashboard-wrapper.test.tsx— 2/2 passe2e/onboarding-flow.spec.tsasserts onlystart-here-*,onboarding-*, andpost-onboarding-*testids — none of the removed/renamed UI; no e2e or unit test references "Activation Progress", the old checklist title, orgetting-started-checklistinternalshttps://claude.ai/code/session_01TyMddHGjcjofqS6K9H2MeW
Generated by Claude Code