Website Developer Agent

A website builder that understands the live system.

The Website Developer Agent builds inside Salesbooth’s native site model: shared presentation in the site shell, page-specific content in page records, a protected preview, and approval before publishing.

View plans
Native architecture

Built the way Salesbooth renders websites.

Shared concerns stay shared, pages stay focused, and reusable components have a clear home. That means the preview and the live renderer work from the same structure.

sites

The shared shell

Owns the global head, navigation, footer, branded CSS, and trusted site JavaScript—including the single canonical widget embed.

site_pages

Page-specific content

Stores each page’s semantic body, title, description, path, status, and version without duplicating global presentation.

site_blocks

Reusable sections

Stores repeated page sections once when reuse is appropriate, then expands them for preview and publication.

Draft to live

A reviewable path, not a one-shot overwrite.

The workflow keeps customer-facing changes inspectable at each stage and verifies the committed result after publishing.

01

Plan and draft

Use business context, real products, page goals, and the intended customer journey.

02

Self-review

Check structure, copy, links, responsive behavior, SEO, proof, and widget handoff.

03

Protected preview

Render the stored shell and page content together before the change is public.

04

Approve and verify

Publish only after approval, keep a backup, and verify the live records after commit.

Quality gates

Designed to catch the failures customers actually notice.

The stored site is checked for completeness and convergence, rather than relying on a model saying the page looks finished.

01 / RENDER

Desktop and mobile

Responsive layouts, phone-width overflow, readable type, and complete visible content are evaluated before readiness.

02 / JOURNEY

Links and capture

Dead navigation, placeholder forms, missing widget handoffs, and broken customer paths block readiness.

03 / STORAGE

Stored artifact evidence

The final re-check uses the saved shell and page records that the preview route actually renders.

Widget delivery

Every page can open one trusted sales surface.

The Website Developer Agent never invents a key. Salesbooth provisions an origin-restricted publishable key, stores the canonical element in the shared shell, and lets page buttons open it.

One embed in the site shell.

The custom element is shared across every composed page while page calls to action use simple, accessible trigger attributes.

sites.javascript
widget_loader: canonical
publishable_key: provisioned
allowed_origin: matched

Products stay authoritative.

The widget reads the active tenant catalogue and calculates configuration choices there, keeping pricing out of fragile hard-coded forms.

✓StartupLive product
✓ProfessionalLive product
✓EnterpriseLive product
Practical details

A website workflow your team can trust.

The design can move quickly because publishing and verification are separate, explicit stages.

Does the agent publish while it is drafting?

No. Draft work and protected previews are created before the approval-gated publish action.

Can pages have different SEO metadata?

Yes. Each native page carries its own customer-facing title and description while shared head and presentation concerns remain at site level.

What happens to the previous live page?

The publish workflow records backup evidence before replacement and verifies the committed live rows afterward.

Build inside the product

Turn your next website brief into a native Salesbooth draft.

Tell the widget what the site needs to achieve and which real products or services it should help customers explore.