Website
Build a site around a useful customer task: understand a service, prepare for a visit or reach the right booking page. Start with accurate information and a clear next action, then check the actual page at desktop, tablet and phone sizes.
The example below is a private Maple workshop service guide with three service explanations and a visit-preparation checklist. Its files and heading edit were saved through the editor. It was not published, connected to a domain or generated by AI during this review.
Website Builder
Open Website and choose an existing site, or use New Site to start a separate project. Check the site name before editing so a rehearsal does not replace an established business page.
- Name the project for its purpose, such as Maple workshop service guide.
- If using a creation brief, describe the intended audience, services and next action. Choose the visual direction and image preference deliberately.
- Create the project and wait for its repository files and preview to finish loading. A project card alone does not prove the page can render.
- Open the page selector to choose the route you intend to change.
- Review the desktop, tablet and mobile previews. Check long headings, card order, navigation and the bottom of the page.
- Use Save to review and persist file changes. Follow the separate publishing procedure when the content is ready to become public.

The editor works with actual project files. Source changes can affect multiple routes, shared styles and all preview sizes. Keep a small first page working before adding integrations or more pages.
AI Editor
The site editor includes an AI assistant with page and project tools. Give it a concrete outcome and constraints, then inspect the changed files and rendered result. An accepted request or a message saying work is complete does not replace checking the site.
For the workshop example, a useful follow-up request is:
Add a visit-preparation section below the service cards. Explain how to describe the affected fixture and prepare access. Keep the existing green palette. Do not invent prices, testimonials, contact information or appointment availability.
Ask for a focused change instead of rebuilding the whole site on each request. Review headings, links, images, keyboard access and phone layout after the assistant changes them. Use the save panel to inspect what will be persisted.
The assistant's implementation can edit project files, inspect page structure and work with supported site sections and CMS data. Model access, runtime readiness and any required service connection must work. No AI generation request was run for the screenshots in this guide; the demonstrated page was edited directly in the actual site editor.
Code Export
The reviewed site workspace exposes repository files and a Save workflow backed by the site's connected repository. It does not expose a verified Export Code or downloadable site ZIP action.
To inspect or retain code, open Files, choose the relevant page or stylesheet and review the actual source. Use Save to review the changed-file list and diff, enter a meaningful message and save the changes. Confirm the pending-change count clears and reopen the project to check the saved content.
If you need a local checkout, use the connected repository through your authorized repository tools. Repository access, a source checkout and a production deployment are separate requirements. Do not assume a preview URL or a saved site card is a portable export, and do not treat an unrelated builder's ZIP download as website-export support.
A standalone website export procedure remains unverified in this version.
Site Publishing
Save persists edits; Publish requests a deployment. Complete the content review before using Publish because it can make the site publicly accessible and connect its configured domain.
- Review the intended project and route. Test navigation, links and any real form or booking destination.
- Save all pending changes. The editor blocks publication while unsaved changes remain.
- Open site settings and check the site name, description, favicon, social image and intended domain.
- Confirm any custom domain is a verified managed business domain. Domain registration, verification and site publication are different steps; see Custom Domains.
- Use Publish when authorized to release the site. Open Deployments to inspect the returned deployment and its progress.
- Wait for a successful build and deployment, then open the resulting public URL. Test its content and customer actions again on a phone-sized screen.
The implementation can update the site record and domain connection while deployment progress is still being tracked. Treat the final deployment result and the actual public address as the evidence that the release works. A Live status label by itself is insufficient.
The workshop site remained Draft with no verified domain connected. No Publish, deployment, domain change or public website check was performed in this review.
Visual Site Editor
Use the visual editor when you can point to the content that needs changing. Select the element in the preview, then inspect its content and style controls. Nested links, headings and containers are separate elements.
The demonstrated workflow changed the real page heading from A clearer start to your plumbing visit. to A better start to your plumbing visit.:
- Select the heading in the page preview and open its inspector.
- Change the Content value and leave the field to apply the edit.
- Confirm the heading changes in the desktop, tablet and mobile previews.
- Review the resulting pending file change in Save.
- Save it with a useful message and check the saved project again.

The inspector shows the selected element's typography, dimensions, spacing and applied styles. A shared stylesheet can influence more than the selected element, so recheck related content after a style change. Image and navigation controls need actual valid destinations; an attractive button with an empty or incorrect link is unfinished.
One-Prompt Websites
A creation brief gives the site builder a starting direction. Describe the business task, the content to include and the facts it must not invent. A clear brief reduces guesswork but still needs a page review.

For example:
Explain drain inspections, leak repairs and visit preparation for a neighborhood plumbing workshop. Use green. Do not invent prices, reviews or contact details.
Choose My photos only when you want the creation process to use your own imagery. Supply suitable authorized photos rather than assuming the preference creates them.
The implementation hands a nonempty creation goal to the site assistant after project setup and runtime startup. That handoff does not guarantee a complete usable site in one pass. Check every claim, image, customer link and breakpoint before saving and publishing. End-to-end prompt generation was not exercised here.
Site CMS
CMS keeps repeatable site content in a bank: for example preparation articles with Title, Body and Image fields. This lets content be managed as entries instead of manually changing repeated page code.
Open Content in the editor to connect an existing bank or choose Create New Bank. Site settings also offers starting schemas for blog posts, page sections, a gallery or FAQs.
- Decide which information belongs in the collection and which may safely appear on a public site.
- Search for the intended bank, or name a new one and review its schema.
- Choose field names and types that match the page. For preparation articles, start with a title, explanatory body and an optional suitable image.
- Review Create & Connect before submitting: it creates a bank and links it to the site. Selecting an existing bank also saves a connection.
- Add meaningful entries and ensure the page is actually bound to those fields.
- Check the rendered site after changing an entry. A connected bank does not automatically turn every manually written card into CMS content.

The content manager supports entry editing and the site tooling can generate a public-read content helper. Review what the site will expose before connecting a bank; keep customer records, private notes and credentials out of public content collections.
This review inspected schema setup and source behavior without connecting the rehearsal bank or generating its public data helper. Entry persistence, live data binding and public CMS delivery were not tested for this site. See Banks for the underlying collection workflow.
Site Section Builder
The site assistant has implementation support for reusable sections including before/after comparison, a price estimator, reviews, FAQ, a sticky action, a gallery, process steps, a video hero, reveal effects and contact content.
Request a section by its purpose and provide real content. For example, ask for three visit-preparation steps using the business's approved wording. For a before/after comparison, provide both authorized images and accurate labels. A reviews component requires genuine reviews; its availability does not justify inventing endorsements.
Section tooling prepares a component and stylesheet, preserves an existing section file instead of overwriting it, and returns the import and usage information needed to place it in a page. Creating files is only one step: the section must be inserted, receive its content and render correctly in the intended route.
The reviewed workspace's draw tools also offer containers, text and image elements. A dedicated manually tested section-template insertion workflow was not established here, and no assistant-generated section was executed for these screenshots. The workshop's service and preparation sections are real rendered page content, not evidence that every reusable section was exercised.
Site Layer Editing
Open Page tree to understand the page hierarchy and find a nested element that is difficult to select directly. The workshop tree shows its main container, header and navigation, service articles, preparation section and footer.

Expand the relevant branch and select the intended child. Confirm the highlight in the preview before editing: changing a heading, its enclosing link or the whole section produces different results. Use the inspector to check content and layout after selection.
When rearranging content, check the containing element, reading order, responsive layout and keyboard navigation together. A visually moved item can still have an unexpected reading order or affect another breakpoint. Save a small reviewed change before making a broader structural edit.
Troubleshooting
| Symptom | What to check |
|---|---|
| Project opens but preview is blank | Wait for files and runtime readiness; inspect terminal output. The reviewed project needed the available Restart container control after a reopen before its healthy preview returned. |
| Preview shows a runtime or hydration error | Inspect the actual error and affected code. Resolve it before accepting the screenshot or publishing; a visible page under an error overlay is not a clean result. |
| A visual edit disappears | Confirm it became a pending file change, completed Save and belongs to the project and route you reopened. |
| Publish is blocked | Save all pending changes, then check repository access and deployment requirements. |
| Status says Live but the URL fails | Inspect the final deployment result, actual address and domain verification. |
| CMS panel has fields but page content is unchanged | Confirm the correct bank, meaningful entries and an actual page binding. A schema draft alone does not publish content. |
| A code download cannot be found | Website ZIP export was not verified; use the connected repository workflow where available. |