Page Studio

Agency staff work from a portfolio view protected by explicit Page Studio permissions. The independent CMS shares the Page Studio design, starts in light mode and remembers each browser’s light or dark appearance. Invited customers can sign in directly at the Page Studio product entry and choose an assigned website from My sites. Agency administrators manage each website’s invited-user access from the client website portfolio, with explicit view or edit permissions, recorded access changes and a direct Open CMS link. Invited users verify their own email; an agency session does not sign them into the CMS. In the limited signup preview, new customers choose their website topic and goals before creating an email account. The topic list includes Automotive, and goals include vehicle stock, test-drive requests, events and recruitment. The standalone workspace preview groups saved pages and SEO details, a searchable image library with private previews and form enquiries, with links to connected content tools and draft history. The limited native customer Forms preview adds a Manage forms entry for eligible website owners when access and saved workspace setup are ready. It reuses draft outcomes, recipients and separate team/customer templates; native enquiries, hosted acceptance and delivery activation remain pending. The invited-customer local demo separates Forms settings from the Enquiries inbox. Adopted reusable forms appear once with their page placements, shared draft outcomes and a combined enquiry filter. The local preview also supports website-wide team recipient drafts, explicit shared-form overrides and an impact summary; these do not enable email delivery. Website team and customer template drafts add one-click content blocks, brand styling, undo/redo and safe live desktop/mobile previews that update as you edit with example answers. The draft editor separates Content, Design and Details, with Clean, Warm and Classic looks, enquiry starting layouts and optional business headers, contact footers, social links and disclaimers. Shared forms can inherit the website template or save a custom team/customer draft for all their page placements, with an explicit reset to the website default. Website-default changes preserve custom form templates. The local editor lists templates left behind by removed shared forms; customers can remove individual templates, undo a pending removal and explicitly save the cleanup. Existing shared forms keep their templates even when they have no page placements. The local editor also offers a saved revision browser for website and shared-form team/customer templates. Review an earlier version with example answers, then explicitly use it as an unsaved draft; saving adds a new revision. The audience-wide log includes saves to other form templates, while restoration changes only the selected template and preserves current custom overrides and staged cleanup. A form version without a custom template restores inheritance of the current website default. Read-only members can browse revisions. Nothing is emailed or published. In the local demo, choose a logo or photo from the website library, add alt text, adjust its size and alignment, and review it in the isolated email preview. Local AI email design work adds an explicitly configured model picker and real monthly allowance checks. Describe a change, review a proposal with example answers, then choose Apply to add an unsaved edit with Undo and Save. Manual changes make older proposals inapplicable; generation never sends email. The local template editor offers saved form-field text with explicit fallback content. Choose a field and insertion target, review the example preview, then use Undo/Redo or replace the reference with fallback text as an unsaved edit. Field labels can change without breaking references, while removed or changed fields require review. Controls appear only when the current website and installed preview services support them. Hosted availability remains pending. Hosted AI enablement, native customer AI access and sending remain pending. It includes draft messages, conditional same-site redirects and outcome previews; hosted activation and live delivery remain pending. Visual editing opens separately when the editor connection and editing access are available. Existing client portal access remains available, and every request stays scoped to that client and membership. Internal provisioning and release controls never leak into the client experience. In the limited standalone customer preview, eligible owners can open their saved draft from the website overview when editor access is enabled and managed storage passes verification. Opening Studio does not publish the website; broader customer rollout remains subject to staging acceptance.

The website workspace shows the pages, SEO and form counts from your saved Studio website. The local editor preview adds Pages/Sections thumbnails and a grouped page overview. Collapsed navigation joins the bottom toolbar, and Show restores the thumbnail panel; this preview is awaiting the batched native release. Open Studio to edit the same draft, then return to see the latest saved changes. Build a complete page tree with nested subpages, responsive desktop, tablet, and mobile previews, page visibility, shell inheritance, and per-page SEO. Compact preset galleries add canonical sections, page layouts, headers, navigation, mobile menus, footers, themes, and complete site starters as ordinary editable content. AI proposals use the same typed components and controlled operations as manual editing, while revision-safe checkpoints prevent one session from silently overwriting another. Draft history lets authorised editors name a saved version and restore earlier saved work as a new draft, preserving previous checkpoints and the live website. Preview-only edits must be saved through supported controls to appear in history.

Open Components, select a component in Page outline, and use Design to save its supported visual settings with the website draft. Refine typography with text balance, alignment and decoration; choose bento or masonry grids and column counts; apply image masks, filters and blend modes; and adjust corners and link treatments where supported. Layouts collapse in narrow containers, and masonry content reads top to bottom. AI proposals use the same bounded, validated design choices as manual editing, so proposed changes remain editable in Studio. Where custom component generation is enabled, your pending request remains available after closing the editor. Reopen the component library to check its result without starting another generation; discard it explicitly before using more AI allowance. When updating an existing collection, review its private fields before saving. Newly private fields are hidden from current and restored page versions immediately, while stored records are preserved.

Drafts, editor sessions, checkpoints, reviews, approvals, server-owned builds, and immutable releases are separated so editing does not silently become production. Agency editors can name the current saved draft and submit it for review in one action; ordinary named versions remain drafts. The launch checklist brings saved content, current approval, enquiry forms, domain and HTTPS status, email setup and website access together. Reviewers compare saved page, component, form and site changes with a named live release, then approve, reject or return the version to draft. Changed checkpoints and release pointers require a fresh comparison. Publishing checks the exact saved version and current release again before proceeding. Where approved-build review is enabled, publishers prepare the website, open its authenticated preview, confirm their review and publish that exact build. Reopening review recovers the retained build, and short-lived preview access ends when the originating login or publishing access is revoked. Saved form definitions and email preferences remain distinct from verified receipt and delivery tests. XeroFlow verifies the approved R2 checkpoint. Runtime-enabled sites render through Astro on Cloudflare: saving stays private, explicit publishing selects an immutable version, and restoring a retained release preserves newer draft edits. Ordinary content publication does not run a website build.

Preview the saved website at its own stable XeroFlow address before connecting a custom domain. Agency editors and eligible client editors can update staging from the website workspace; viewers can open a ready preview. The workspace distinguishes an assigned address from a verified deployment and shows when the saved draft has changed. A failed update keeps the previous successful snapshot available. Staging previews exclude private pages, carry a visible preview banner and discourage search indexing. Form submissions are disabled in this preview rollout. On runtime-enabled websites, agency publishers share approved versions immediately and can restore earlier releases without rebuilding. Static staging and release builds share the website package allowance; retrying the same accepted build request does not consume another build.

The delivery architecture uses Cloudflare Workers and Pages for build, sandbox, control and delivery services. Agency staff and eligible customer administrators or managers with website editing access can connect a domain and check separate ownership and HTTPS certificate verification records, plus the configured website DNS target. Copy controls provide each record name and value, with TTL and external-provider guidance. The website dashboard includes a Domains & Launch section with the same site-scoped controls. Customers can follow guided paths for existing domains, Cloudflare DNS migration, registration transfer and domain purchase. Registration and payment take place in the customer’s Cloudflare account. Portal viewers can read the connection instructions, and customers without custom-domain capacity see the required access clearly. Website publication remains an agency-controlled action. Activation requires matching DNS, verified hostname ownership and an active certificate. Connecting a website preserves existing email records; customer email setup and domain cutover remain separate rollout steps.

Connect CMS storage to an existing website from its agency workspace or client admin, preserving saved pages and website history. Manage collections such as services, fleet and testimonials for the selected website. Editors can maintain descriptions and typed detail fields, while viewers have read-only access. Revision checks protect changes made in another session, and unsaved drafts remain available after a conflict. Saving content prepares a draft; publication still requires a governed release. Eligible websites with custom collection setup enabled can define text, number, choice and date fields, edit entries through generated forms, archive records and restore earlier values as a new revision. Schema changes require stronger management access, and websites awaiting a reviewed runtime show setup as pending. Where runtime CMS publication is enabled, publish an approved component template once and show its current public collection records without rebuilding the website. Archived records and fields made private stop appearing. Restoring an earlier website release retains the latest collection records.

Agency staff can open a website enquiry to inspect every recorded field alongside its receipt, form, page and submission time. Filter the loaded inbox by live or test submissions. Long responses remain readable in a scrollable details panel. Viewing a receipt does not resend a notification or confirm a booking.

Agency editors and eligible business administrators or managers can save sender identity, a team notification inbox and optional incoming forwarding preferences for each website. Revision checks protect against overwriting another editor’s changes. These preferences show email setup as pending: saving them does not verify a sender, send messages, change DNS or enable forwarding. Provider verification and delivery setup remain agency-managed prerequisites.

The website booking queue lets authorised agency operators review enquiries, save quotes with an expiry date, and record approval, rejection, cancellation and completion decisions. Signed-in business administrators and managers with website editing access can record customer enquiries in their portal and resume the same request after an interrupted response. Each view belongs to the selected website and requires active booking access. Updates check the current booking version, and retries retain the same request so delayed responses do not create duplicate actions. Vehicle reservations, trip confirmation and customer notifications remain separate operational steps during the staged rollout.

Staff can prepare and revise a website setup plan from a starter or brief, review its pages and modules, and keep unconfirmed business details visible before launch. Eligible customer administrators and managers can create a website from a business template or brief. The draft, editor access and initial review proposal are saved together only when subscription limits allow them. Customers with website editing access can submit business details and revised plans from their portal; viewers can read the plan and progress. Agency approval is tied to the current revision. Where the setup service is connected, staff and authorised customer editors can explicitly request preparation of the approved revision and track its progress. Authorised agency staff can record a client’s website access period, permitted modules and limits for sites, pages, storage, domains, AI operations, builds and traffic. Trial access requires an expiry, while client website creation can be enabled separately. Each grant records its reason and actor in the billing audit; matching retries return the original result and competing grants cannot replace existing access. These access grants do not create charges or a paid billing subscription. Renewal, plan changes and provider billing remain separate rollout work.