Draft public pages with Site Studio

A website change needs a private place to prepare copy, inspect the layout and review the version to publish. Open Site Studio → Edit installation website for that workflow. Installation owners manage the public website; other workspace admins can use their private page drafts.

Create and edit a page

A new full-repository fork starts with an editable Command Center homepage. Use Identity and Theme to make it your own, then customize the homepage sections or add pages. Agency content stays disabled unless the installer explicitly selects the branded distribution. Saved drafts and published revisions remain unchanged when the deployment profile changes.

1. Select Add page, enter a title and page address, and choose a service, landing or article starter. Clone page copies the current page into a new address.
2. Edit the page fields and search description. Open a section to change its text or appearance; add, reorder, hide supported native sections, or remove sections as needed. Article controls support headings, paragraphs, formatted text, lists, quotes, code and images.
3. Use Ask AI to improve copy while retaining the layout, or generate a new layout and copy. Describe the result you want, choose a model, and prepare a suggestion. Review the changes and choose Apply to draft. Preparing or applying a suggestion does not publish it.
4. Check the live preview at Phone, Tablet and Desktop widths. Undo and Redo recover local edits. Select Save draft to create a private, versioned snapshot.

Example: draft a bookkeeping service page

For example, create a service page at /bookkeeping-automation. Ask AI to “Explain how this service reduces evening admin work, using plain language and no invented prices or results.” Review its suggested copy, apply it, check the phone preview and save. The next step is a separate publication review.

The bundled homepage exposes its existing sections. Other bundled routes retain their source content until a published page explicitly replaces that address; they are not automatically imported as editable copies. Replacing a route requires reviewing its existing forms, links and metadata. Application routes, documentation routes and compatibility redirects cannot be replaced from the editor.

Check a saved page on a phone after opening it, visiting another page and returning, so the review includes repeat visits. Fresh public visits replay their entrance, while Back and Forward keep restored content readable. The branded homepage hero uses one consistent headline size and typeface, with balanced wrapping across desktop and phone screens. It fills the viewport and expands when its content needs more room. Three ribbon forms move at different paces, while a pointer or tap shifts and illuminates the background field. The artwork pauses offscreen and behind the mobile menu, so it remains quiet while you navigate. Touch screens use static media depth and crisp section entrances. Device reduced-motion settings and unavailable JavaScript show complete static content. Your saved copy, theme and section order continue to control the published page.

Choose a model and control cost

DeepSeek V4.1 Flash is the default. You can choose another model whenever the page needs a different tradeoff. Recommended choices include free Nex models, very low-cost Mercury and DeepSeek, GPT-5.6 Luna, Gemini 3.8 Flash, Claude Sonnet 5, Opus 5, Fable 5.1 and GPT-6 Astra. Choose Browse all models to search names or model IDs, filter by provider and cost, and sort by newest or lowest token price. You can return to Recommended models at any time. Recommendations follow the newest compatible members of these model families; refreshing never changes your selected model ID.

Refresh models reads the current OpenRouter catalogue without making a paid generation request. Compatible new models appear without a code release. The list includes text models with structured-output support and known pricing; automatic routers, batch, Contributor and incompatible variants are excluded. The catalogue status shows when it was checked. If refresh fails, a dated saved catalogue remains available. A removed model is never silently replaced.

The displayed input and output rates are per million tokens. Generation rechecks compatibility and uses the prices you reviewed as ceilings. If prices rise, refresh and review before retrying. Availability may vary, especially for free models.

Connect OpenRouter under Setup to make real model calls. Requests use the shared model gateway, usage receipts and workspace budget. The chosen model does not silently switch to a more expensive one. Provider costs can apply even when output fails validation. Built-in starters, manual editing and previews make no model request.

AI changes must pass the same content validation as manual edits. Copy editing preserves page identity, addresses and layout. Review factual claims yourself: validation cannot establish that every business claim is true. If generation fails, keep editing manually or deliberately select another model and retry. No failed suggestion changes the saved draft.

Publish and recover

Save your changes, then select Review publication. Review the saved page list and responsive previews before selecting Publish saved revision. The exact saved revision becomes public; subsequent draft edits stay private until another publication.

Public pages reuse the published revision between visits. Publishing, rollback and unpublishing request a refresh for the next visit; saving a draft does not change public pages. Periodic revalidation provides recovery if that refresh is unavailable. After publishing, open the public page to check its content. If it still shows an older version, reload and check History for the recorded publication before retrying the change.

History lists recent revisions. Review rollback restores a previously published version while preserving the current draft. Unpublish removes public website availability while retaining drafts and history. Review each confirmation before continuing. The scoped MCP connection described below supports these same saved website operations; scheduled publication remains outside this editor.

Edit from ChatGPT

When you want to describe a website change in conversation, the installation owner can connect a supported ChatGPT web workspace to the same editor services after the installer configures OAuth. Custom MCP apps are currently unavailable in the ChatGPT phone app. The connection covers pages, sections, copy, layouts, search metadata, navigation, branding, assets, collections, portable documents, publication and history. For example, ask it to clone Ledgerstone's bookkeeping page, revise its introduction and save a private draft, then review the returned changes before requesting publication. Check OpenAI's current MCP availability before setup.

Ask the installer to follow the ChatGPT connection setup, then open Site Studio → Connect ChatGPT to review access. The connection lasts 30 days and can be revoked from that screen. The five editor tools read current content, prepare an exact preview, stage it, execute it under your delegation, and optionally request an AI suggestion. An outdated version requires a fresh preview, so concurrent edits remain protected.

ChatGPT manages its write confirmations, while the server records which owner and connection delegated the action. Delegation permits saving, deleting content, publishing, unpublishing and restoring website revisions. Its scope excludes workspace records and the separate tenant-owned page draft list. Legacy workspace MCP keys retain their proposal-only write behavior. AI suggestions use the same model budget, price ceilings and generation limit as the editor; manual edits make no model request.

If the network drops after a write, use Retry same save or the corresponding publication retry. It reuses the original request, avoiding duplicate revisions. An edit conflict preserves your local fields. Export draft before Reload saved draft if you want to retain a copy; reload asks before replacing local edits. Save and publish errors remain visible until resolved.

Open Website tools for reload, import, export and the saved preview. On phones, switch between Edit content and Preview page, and use Editing to choose the content area. Unpublish is available inside History.

Shared content, assets and collections

For a service or landing page, open Connect a form, choose Load published forms, select a form from this workspace and choose Add form section. Publish the form in Form Builder first. The page uses the existing submission and review workflow, so you can inspect the response and accept it into intake from the same workspace. Preview forms display their connection without accepting responses; test the published page with controlled data after publication.

The website supports eight distinct forms. When a form is archived, its module is disabled, or its connection is unavailable, the page displays an unavailable message. Reconnect the form or remove its section before saving or publishing again. Imported websites need form bindings from the destination workspace. Website tools links to Setup and the optional ChatGPT connection, and lists the steps from business identity through the first controlled submission. In neutral mode, use images under public/site-assets/ or an approved HTTPS origin; the agency image namespaces are disabled.

Use Identity, Navigation, Footer and Theme to edit shared branding, links and appearance. The preview and published output share their theme settings. Under Assets, add an image path or HTTPS image URL and an accessible description, then use it as a logo, sharing image or article image. The asset manager references existing image files; it does not upload files. An image still referenced by content cannot be removed.

Collections organize repeatable articles and case studies. Create a collection, add an entry, edit its page address, search fields, tags and article body, then save and publish the website. Published entry addresses render as article pages. Published pages and entries are included in the sitemap unless Hidden from search is selected.

Move content to your own installation

Export draft downloads a portable snapshot containing content, appearance and image references. It excludes credentials, workspace permissions and publication state. Image files are not included; make referenced files available in the destination installation.

Choose Import draft in your own installation, review the imported content, then save a private revision. Import never publishes. Invalid snapshots, unsafe links and files over 8 MB are rejected while preserving local edits. A credential-free fork starts from its own bundled content and does not contact Accelerate's database.

Private workspace drafts and the fictional demo

The original Site Studio draft list remains available for tenant-owned service drafts. Enter a brief, choose a built-in template or AI model, attach approved catalogue photography and create a draft. Its preview supports rename and discard. These drafts are separate from the installation website and do not publish from that screen. Section regeneration is available through its authenticated API with a required checksum and a supported model ID.

In the full admin demo, open the installation website editor to try creation, fictional AI suggestions, saving, publication receipts and rollback. Changes remain in that business scenario's browser session. They do not publish a live website, contact a provider or mutate production records. Switching scenarios isolates their drafts; resetting removes the scenario's changes.

What to check

Verify the exact preview and publication summary in ChatGPT before executing a change. Check the returned revision and receipt afterward, especially after a network interruption. Repeat an uncertain execution with the same action ID, digest and summary; if content changed, prepare and review a new command. ChatGPT client support and confirmation settings vary, so the installer must verify the intended client against the deployed connection before relying on it.

If saving fails after an installation upgrade, ask the administrator to verify the application and database versions together. Saves use the verified server identity and the current workspace membership, so your saved revision keeps the correct author. Existing installations with the temporary authenticated-write grant need the compatible application released before that grant is removed. Keep the draft and inspect its saved revision before retrying an uncertain response.