Wizard
Usage
A multi-step flow built on the existing `Stepper` — the layout and navigation a form gets when it is too long for one screen, not a separate visual language. Steps are supplied as content; validation per step is the caller's responsibility (gate `onComplete`/the Continue handler however the flow needs).import { Wizard } from '@summonware/ui';Best practices
DoKeep each step to one clear task ("Contact details," "Payment") — a wizard with a vague step boundary defeats the point of splitting the form up.
Don'tUse this for a 2-field form. A wizard adds navigation chrome that a short form does not need — just use `FormSection`.
Examples
Common configurations, variations and states.Account setup
Three steps, built from ordinary form fields — the wizard only owns navigation.