How many steps is too many?

More than about four without a visible finish line. If you need more, group them and show the group progress — people abandon on an unknown remaining count, not on effort.

Should onboarding be skippable?

Always, and the skip should be honest rather than a guilt-tripped "no thanks, I like being confused". Put the checklist somewhere permanent so skipping is deferring, not losing.

Are these onboarding flows free to use?

All 8 are free to copy and use in your own projects, including commercial ones. A Pro licence exists for redistribution — shipping them inside a product other people buy — and the full terms are on the licence page.

How do I add one to my project?

Install it with the CLI: `npx hoverlab add onboarding-checklist` writes the component and its dependencies into your project. Every artifact here also has a copy button for the raw source, and an "Open in sandbox" link if you would rather try it first.

Finish setting up

Five short steps and your workspace is ready to use.

Setup progress1 of 5

Create your account
Done — welcome aboard.
Create your first project
A project holds your environments, keys and deployments.
Start2 min
Install the CLI
One command, and your terminal can deploy.
Start3 min
Invite a teammate
Projects are more useful with someone to share them with.
Start1 min
Connect a domain
Point a hostname at your first deployment.
Start5 min

Setup Checklist with Progress

The get-started card that ships with its first item already ticked, a native <progress> element rather than a div bar, and a dismiss control that appears only once there is nothing left to abandon.

Onboarding230 lines1 dep10 Sept

Step 3 of 4

Bring your team in

Paste as many addresses as you like — commas, spaces or one per line all work.

Email addresses

priya@northwind.com

1 person will be invited to Northwind.

Invite everyone as

Can build and ship. The right default.

https://app.example.com/join/northwind-8f31c2

Invites expire after 14 days and can be revoked from Settings.

Team Invite Step

The onboarding step where a product becomes multiplayer: pasted addresses split into chips, typos marked rather than dropped, and an honest way to skip.

Onboarding279 lines1 dep10 Sept

Guided Setup Wizard

A choice-driven wizard with a persistent side rail, real radio groups in a fieldset so arrow keys work, and visited steps navigable while steps ahead stay out of the tab order.

Onboarding265 lines1 dep10 Sept

Product Tour Coach Mark

A tour step anchored to the control it explains, with a spotlight cut by one spread shadow, a visible step count and focus that follows the step.

Onboarding262 lines1 dep11 Sept

Step 1 of 3

What will you be doing in Northwind?

This sets what you see first. Nothing here is locked in.

EngineerOpens the code panel first, installs the CLI, and shows diffs instead of previews.DesignerOpens the canvas first, hides the code panel, and turns on the Figma import.Product or project leadStarts on the roadmap view, and weekly summaries are switched on by default.Operations or supportStarts on the queue, with keyboard shortcuts and bulk actions enabled.

Whatever you pick, you can change it in Settings → Workspace at any time.

Role Picker

The "what best describes you" step, asked honestly — every option states what it actually changes, the skip is visible and names what you get instead, and the choice is reversible.

Onboarding191 lines1 dep10 Sept

Step 2 of 4

Bring your data across

Or don't — a sample workspace is a perfectly good way to look around first, and nothing here is permanent.

You can add or change a source at any time in Settings — this is not a one-off decision.

Import or Start Empty

The empty product’s real first question. Sample data is offered with equal weight rather than as grey small print, every connector names its scope before the redirect, and each option carries the honest duration.

Onboarding216 lines1 dep10 Sept

Workspace Setup Form

The first screen after signup, asking only the two things that cannot be changed silently later.

Onboarding176 linesNo deps

Switching

We move it, and we say what we cannot

Every migration page promises everything comes across. Something never does, and finding out which thing after the cutover is how a switch becomes a rollback.

Records, history and attachmentsEverything with a stable id, including the timestamps, so reports still line up.
Users and their permissionsRoles are mapped, and the mapping is shown for approval before anything is written.
What does not come acrossCustom automations. The triggers have no equivalent here and a silent half-migration is worse.
Run it twiceA trial into a sandbox first, then the real one. The trial is free and does not count against anything.

Data Migration Split

What a migration actually moves and what it cannot, stated before the switch rather than discovered after it.

Onboarding158 linesNo deps13 Sept

Onboarding flows

Blocks8