Discovery, templates, and private publishing

Template discovery index

Single API entrypoint for finding page templates, site-template groups, starter sites, clone manifest examples, conversion handoff fields, and future webhook context.

Page templates

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

Site templates

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

Example sites

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

Themes

Theme catalog with source filters, Cloud Elephants coverage, preview URLs, swatches, layout settings, accessibility metadata, and optional full theme payloads.

Recipes

Recipe catalog from the template recipe review model, including coverage status, polish summaries, colorways, gaps, and optional compatible templates.

Quality gate

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

Full starter site

Start from a complete industry site when the builder needs routes, forms, assets, globals, and deployment notes together.

Playful candy shop

Use Elsie's Hard Candies when a buyer wants a playful specialty-retail catalog, gift inquiry funnel, and JSON-ready configuration handoff.

Recipe-family preview

Filter by source recipe id while rendered previews preserve that id and emit shared runtime family classes such as glass, neumorphic, or skeuomorphic.

Single lead page

Find the best individual page by industry fit, use case, and visitor intent before fetching a clone manifest.

Site-template group

Fetch the common page-template group when the builder wants compatible pages ranked by aggregate selection metadata.

Funnel preset

Use the common-funnel template when the outcome is guided capture, then choose a lead-flow preset from its existing lead_funnel_flows metadata.

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

Query the quality gate before selecting templates.

Choose by outcome: full starter site, single page, site-template group, or common-funnel preset.

Use /example-sites/:template_id#site-spec-builder when the buyer should submit an ensemble.site-spec.v0 JSON configuration to a third-party service.

Preserve selected source recipe ids such as glass-product, soft-neumorphic, or tactile-service-ledger; rendered previews add the matching runtime family classes for visual QA.

Send buyers who are ready to act into Cloud Elephants new-tenant onboarding with the selected starter-site context.

Query theme and recipe catalogs when the buyer needs to compare look, content density, or coverage gaps.

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

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

Store the generated snapshot in the upstream Cloud Elephants CMS.

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

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