Website builder service

Discovery, templates, and private publishing

Use Ensemble as a public discovery client for blocks, recipes, themes, working templates, clone manifests, quality evidence, and the Cloud Elephants publishing boundary.

builder guidepublic discoveryprivate publish
Discovery map

Public routes a builder can crawl

13 routes
/docs/docs/comprehensive-api/docs/website-builder/block-catalog/block-catalog/{block}/recipes/{recipe}/themes/themes/{theme}/recipes/templates/demo-sites/page-templates/demo-sites/page-templates/recipes/{recipe}/sitemap.xml/llms.txt
Machine-readable APIs

Template and readiness endpoints

clone-ready
API

Page templates

Individual CMS page families with slot models, compatible recipes, colorway routes, component coverage, polish audit, and optional clone manifests.

Open API
API

Site templates

Multi-page template groups assembled from compatible page templates, optional globals, aggregate component coverage, and site-level clone manifest.

Open API
API

Example sites

Complete working starter sites with content roots, pages, globals, assets, forms, validation commands, and static deployment notes.

Open API
API

Quality gate

Machine-readable readiness for authorable blocks, page templates, site templates, recipe passports, accessibility, responsive behavior, and runtime portability.

Open API
Builder flow

From public discovery to tenant build

8 steps
1

Discover routes through /llms.txt, /sitemap.xml, and the docs index.

2

Query the quality gate before selecting templates.

3

Choose page templates, site templates, or example-site templates for the tenant need.

4

Fetch a detail payload with pages, globals, and clone manifest when ready to copy.

5

Replace brand, navigation, copy, images, form ids, theme tokens, SEO metadata, and routes while preserving Ensemble document structure.

6

Store the generated snapshot in the upstream Cloud Elephants CMS.

7

Let the CMS submit the signed publish request to the private build service.

8

Read generated-root and S3 publish receipts after the build completes.

Private handoff

Publish through the Cloud Elephants CMS

POST /api/ensemble/cms/publish

The website builder should generate or update CMS-owned snapshots. The upstream Cloud Elephants CMS then sends the HMAC-signed publish request to the private Ensemble build service. Production tenant delivery uses publish_target=s3 and verifies the tenant public URL after upload.

generated/build-webhooks/<request_id>.jsongenerated/build-webhooks/<request_id>.loggenerated/snapshots/<snapshot_id>/snapshot.jsongenerated/builds/<tenant_slug>/<request_id>/static-sitegenerated/tenant-builds/<tenant_id>/<request_id>.json