- Shipped
- 25 de agosto de 2026 às 17:22 UTC
- Author
- kamo
- Commit
- debcba5
The Basics step already asks for a website. This reads it and offers what it finds on the three branding steps that follow, as suggestions the member can take, take one of, or ignore entirely. Nothing is ever applied without a click. The scan state lives OUTSIDE WizardFormData deliberately: that object is stringified into sessionStorage on every keystroke, and a result holds several megabytes of base64 -- persisting it would serialize all of it on every character typed anywhere in the wizard, and blow the quota besides. It fires once when the member leaves Basics, three steps before Logo, so the answer is usually waiting by the time they arrive. Every suggestion says WHERE IT CAME FROM -- "Header image", "Carousel slide 2", "CSS --brand-primary", "From your logo". That chip is the whole design: it is the difference between a system that guessed and one that looked, and it is what makes an automatic read of somebody's website feel like evidence rather than a stranger going through their files. The suggestion surfaces are tinted and hairline-edged so a member can tell at a glance which half of the screen is theirs and which half is ours. Failure renders NOTHING. No website, an unreachable site, a plain page -- these steps are optional and already work, so a member whose site gives up nothing has done nothing wrong. The one exception is a rescan they asked for themselves, and a 429, which is the one failure they can act on. The logo rail is per-slot, not per-step: the compact slot is SVG-only because the backend writes it to a fixed logo.svg key whatever the real type is, so offering it a PNG would be offering a broken logo.