Website

Build and publish a complete website

Approve a brief, review a design sample, finish a resumable build and publish or restore a complete release.

Start with your business

Open Build with AI. Check the business description, who the website should help, what customers should do first and how your business should sound. Add any wording that must appear exactly and claims to avoid. Your existing colours, logo and fonts supply the starting identity.

Choose the venue, menu and ordering app by name. Each connection shows whether usable items are available. An empty or unavailable app needs attention before it can support a required customer action. Choosing a particular app keeps that choice explicit.

Choose whether to use existing images or allow image generation, then approve the brief. Generated imagery and replacement design samples can incur AI costs under your company's configured allowance.

Review the first page

The build plans the whole site before writing its pages. It pauses after the first page so you can open a design sample, including the header and footer. Check it on a phone-sized and desktop-sized screen.

Approve the direction to continue, or describe what should change and request another sample. Nothing in this process publishes your replacement site.

You can leave and reopen a build. Completed pages are saved. Resume continues an unfinished or failed build; Cancel stops further work after the active step. Already completed provider work may still be charged.

Preview and edit a candidate

When the build finishes, open its candidate in Releases. The preview link keeps you within that version of the website as you navigate between its pages. Links expire after 24 hours; reopen the release to get another.

Edit headings, text, image descriptions, links or widgets using the candidate editor. Advanced HTML/CSS is available for layout changes. A shared header/footer edit lists the pages it affects. Saving changes or asking AI to repair a page creates a new candidate so the previous version stays available.

For ordinary page work, keep using Pages. Releases can also capture current editor drafts into a candidate for whole-site review.

Check and publish

Review the publication findings and run browser checks. These check every page at phone, tablet and desktop widths. Correct blocking failures and run the checks again on the candidate you intend to publish.

Open the preview yourself to review the wording, images, forms, external embeds and main customer journey. Automated checks do not decide whether a design is right for your business and do not submit forms or make purchases.

Publish this release switches the approved pages, navigation, design, shared header/footer and reusable content together. It does not change your coming-soon setting.

If the live site changed while you were working, publication pauses. Review the listed changes and the current live site. You may create a new candidate keeping your proposed content against the latest live version; publishing that candidate will replace the intervening changes. The new candidate needs its own checks.

Restore a previous state

On a published release, choose Review a restore to before this release. This creates a candidate showing the website as it was immediately before that release. Review, check and publish it like any other candidate.

If the site had no public pages before that release, restoring it returns the site to an unpublished state. The review warns you before publication.

Keep reusable information consistent

Use Collections for FAQs, services, team profiles and campaigns. Add or reorder entries, select images and review where the collection is used before publishing an update. Previous values can be loaded back into the editor for restoration.

Bind an Interactive content widget to a collection to reuse those entries as an FAQ, tabs, carousel or selection guide. The same widget can also hold local entries used only on one page.

Use Venue details for the selected venue's address, phone and ordering hours. Enquiry form connects to an existing published public Forms form. Menu board can offer search and category filtering while retaining the source menu's items and prices.

Updating a published collection or individually publishing a page updates the live site through the normal editing flow. An already-saved release candidate keeps its own snapshot until you explicitly create another candidate.

Protect the brand across AI edits

Open Design → Brand protection. Select which current colours, fonts and logo to protect, and enter wording that must remain exact. Confirm and save the policy. It applies to this site’s AI generation, restyling and regeneration. To change a protected element, deliberately unlock or edit it here first. Check the saved values before generating another page.

Create easier-to-edit templates

Open a section in Library. Declare named text, image and link fields using the elements already present in the section. Save the current CSS as a named style when you want reusable layout choices. Future copies expose those fields and styles in the page and release editors. Advanced HTML/CSS remains available. Review the listed placements and previous versions before saving; existing page copies are changed by deliberately replacing them in a page draft.

For product-specific website copy, create a Product presentation collection. Choose each operational product and its website description/image, then bind the collection in a Product showcase widget. This leaves its name, price and availability controlled by the ordering system.

Check the intended customer action

Select each candidate page’s primary action: explore, order, visit, enquiry, service, event or gift card. Browser checks exercise native controls and inspect the connected public destination. Fix missing product/app/form bindings before publication. Event entry uses the ticket product sold through ordering.

To get a visual second pass, opt in to Visual review before queueing browser checks. Screenshots are sent to your configured model and count against the existing AI allowance. Only findings and review records are retained. The review covers phone and desktop views of up to eight pages, with a height limit; remaining areas need your review. A reported section can be repaired into a new candidate, which must be checked again. Always review the design yourself and test real submissions or checkout with suitable test data before launch.