Private Pro category · 6 compositions
Onboarding
Progressive first-run setup, preference, import, and invitation flows. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 6 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Role and goals
Data import checkpoint
Team invitation
Theme preference
Ready to begin
Category contract
- Purpose
- Progressive first-run setup, preference, import, and invitation flows.
- Declared dependencies
- gummy-progress, gummy-field, gummy-button
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Onboarding blocks
Use an onboarding composition to reduce the first meaningful task into a small, ordered set of decisions: initial setup, preferences, import, or invitation. Explain why information is requested and allow customers to postpone steps that are not required for a safe account.
Persist progress server-side where cross-device continuity matters, validate authorization again for invitations and workspace changes, and separate completion from background processing. Back, skip, retry, and resume behavior should be explicit; progress decoration must not be the only statement of state.
Test a new account, returning account, invitation, interrupted import, expired session, insufficient permission, provider failure, and completed setup. Check keyboard focus after each transition and ensure sample data, team names, or apparent success cannot be confused with real customer records.
Map each step to its durable data, validation, authorization, optionality, and resume rule. Include copy for previously completed work, expired invitations, background jobs, and support escalation. Progress should come from stored outcomes rather than the current screen index, otherwise a refresh or provider retry can tell the customer that unfinished setup is complete.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.