Your project: Cedar Workshop needs a home page, an About page and a contact action. Start with the home page and verify a saved draft before expanding.
The website-wizard entry was captured previously. The detailed control names below were also checked against the current create-website-step.tsx implementation. A completed new-site creation, publish and custom-domain test remains unverified; this is not a claim of a finished live website.
1. Start with the correct site
Sign in to Studio Manager and check the active site. Open Setup Wizard › Build my website. If the wizard reports No site is selected yet, select a site from the dashboard and return. Do not accidentally edit another existing site.
2. Name your website
In Name your website, enter a meaningful name and description. For example: Cedar Workshop — weekend creative classes. Click Save and continue. The title is used in the browser tab and search presentation; it is not the same thing as assigning a custom domain.
3. Choose how to start
| Design route | AI route |
|---|---|
| Browse a starting template. Categories in the implementation include home, landing, about, services, store, blog, listing and form. | Describe the business, audience, desired content and next action. |
| Select a specific page design. | Example: “Build a home page for Cedar Workshop. Explain weekend classes, show the instructors, and include an enquiry action.” |
| Continue to Create the page. | Continue to Let AI build it. |
These are two starting routes in the website wizard. The AI route here opens Build Studio with the brief; do not confuse it with a separate Vibe Studio login.
4. Create the first page
Use Create my page for a selected template, or Build it with AI for the AI route. Wait for the saved page result. A template request that returns no page is an error; select another design or record the failure instead of continuing with a nonexistent page.
On the AI route, a saved empty page is created before the brief is handed to the editor. Inspect the generated result. Generation does not mean the page is published.
5. Make it yours
Choose Edit in Build Studio from Make it yours, then go live. Change the heading, copy, images and primary action. Build Studio supports components, forms and live-data bindings. Keep the first page focused: a promise, evidence and one next action.
Save and reopen the page. If it contains a form, identify which record it should create and inspect that record after a test submission. A button that looks correct is not proof the workflow is connected.
6. Add the other pages and navigation
Use the Add more pages route from the setup checklist or Build Studio. Create the About and Contact pages, set readable names/slugs and link them from the site’s navigation. Follow each link in the rendered preview. Test mobile navigation as well as the desktop layout.
7. Preview, publish and connect your domain
- Use Preview in Build Studio — it opens
/__preview/page/<site>/<page>on the active site, for signed-in staff — and inspect desktop and mobile, images, headings, navigation and the form/action result. - Review the page’s publishing lifecycle and publish controls in the current build; confirm the intended page and site.
- Open Put it on your domain / Domains. Use the domain instructions returned for your environment; do not invent DNS values.
- After publishing, load the public URL in a fresh signed-out window and repeat the navigation and form checks.
Custom-domain and publishing controls still require a fresh end-to-end capture. Record an unresolved domain or deployment state as an issue rather than calling the site live.
Your completion checklist
- Saved page reopens with your content.
- Desktop and mobile previews are readable.
- Links reach the intended pages.
- A test enquiry becomes the expected record.
- The public site is checked separately after publishing.
Next: Turn on live chat, create a customer dashboard, or the advanced whole-site deployment guide.