First capture to first version

Summary

The main path of the product: from the landing page to a first branch merged into main as a new version. It is the spine of the flow chart in routes.js; the chart's key rows (Start · Onboarding · Editor · Changes) follow it.

Audience

A new person setting up their company's first product.

Entry

The landing page, from anywhere.

Steps

#	Step	Surface	Notes
1	Landing	landing	Start free
2	Sign up	sign-up	Google, or email and password
3	Verify email	auth	A link that works for 24 hours
4	Company	onboarding-company	The company's name
5	Your product	onboarding-product	The way in (URL, images or blank), the sizes, one design or one per size, the stack
6	Capture	onboarding-capture	Open, and roles with test sign-ins
7	Capturing	onboarding-capturing	The site is walked; pages, tokens and components arrive
8	Analysis	analysis	Scores and what to fix first. It changes nothing
9	Journey	journey	The whole product as page frames and arrows
10	Pages	pages	Edit, or ask AI. Every change goes into your draft
11	Review	review	Commit the draft to a new branch
12	The branch	branches	Complete or Delta in every section; settle a conflict; Verify
13	Merge	branches	Patch, minor or major
14	Versions	versions	The new version of main

Exit

A first version of main made by a merge.

Escapes

• From images: each screenshot becomes an HTML and CSS page, then Analysis.
• Blank: no capture; the product opens empty (states).
• Stopping the walk ends the capture and opens Analysis on what was found.

Related

• branch-verify-merge · capture-reads-the-product · onboarding-steps · journeys

Sources

• .context/designs/web/routes.js — flow.start, flow.end, the forward edges and the key rows.