Ensemble catalog

Reusable sections for websites that need to work.

Blocks are the page pieces Ensemble uses to turn offers, proof, forms, FAQs, testimonials, and calls to action into business-ready web pages.

Documented blocks94
Contracts136
Registry entries61
Launch postureready
ensemble · 22
bethsaida-legacy · 47
valuesos-content-studio · 8
shadcn-ui · 59
Readiness proof

The friendly builder still checks its work

Open quality API
Gate

ready

45 of 45 blocks and templates clear the grade-A threshold.

Blocks

29/29

Authorable public blocks using ensemble.block-polish.v0.

Pages

14/14

CMS page templates using ensemble.template-polish.v0.

Sites

2/2

Cloneable site-template groups ready for CMS reuse.

Recipes

116

Cloneable block data recipes with contract-safe structured payloads.

Fields

1515

Mapped block-builder fields across the catalog data recipes.

Editors

528

1407 editable fields with widget, validation, and default-source guidance.

States

696

Default, empty, pending, active, invalid, and disabled-state guidance across block recipes.

Anatomy

544

Surface, copy, media, action, control, metadata, feedback, and collection regions mapped across block recipes.

Passports

116

696 publish checks across cloneable block composition passports.

Polish

696/696

Surface, type, action, media, state, and responsive polish checks across cloneable block recipes.

Defaults

1515

260 high-care replacements with source, risk, and guardrail evidence.

Bundles

528

172 required and 116 guarded edit bundles for coherent CMS replacement.

Fit

696

Page context, section role, content model, interaction, authoring, and responsive fit maps for block recipes.

Actions

118

CTA, link, event, and button surfaces detected in block recipe payloads.

Controls

60

Input and choice controls mapped from recipe-ready block data.

Tokens

1740

Theme token roles proving styled defaults across recipe payloads.

Contrast

696/696

Readability checks proving text, buttons, controls, and badges meet recipe contrast targets.

A11y

580

Semantic, keyboard, media, label, and state checks mapped across block recipe payloads.

Responsive

348

Phone, tablet, and desktop behavior maps proving recipe defaults stack, balance, wrap, and avoid overflow.

Portable

116

29 React, 29 Next/static, 29 WordPress, and 29 package-consumer block support proofs.

Editable

362

CMS-editable page-template fields across generated template pages.

Passports

19

Theme recipe passports with swatches, page types, and rules.

Block explorer

Find the section your next page needs

Alias

22 documented surfaces

23 contracts
Native

71 documented surfaces

74 contracts
Nonvisual Noop

1 documented surfaces

1 contracts
Canonical examples

Real sections, rendered from structured content

Website sections that know their job

Every block has a purpose: sell the offer, show proof, capture intent, or move the visitor to the next step.

This is the plain-copy block: useful for explaining the service, answering the obvious question, and sounding like a person instead of a brochure generator.

Reusable business pieces

Ensemble keeps the page ingredients organized so a business can reuse what works instead of rebuilding every page from scratch.

Clear fields

Each block knows which copy, images, links, and proof points it needs.

Fast pages

Validated content can render into quick static pages for customers.

Smart actions

Interactive blocks can capture leads, clicks, and useful signals.

conversion

Lead capture without the sticky-note pile

Forms collect the context a business needs, while the builder keeps fields and outcomes tidy.

2 fieldsLow-frictionPrivacy aware

We only use your answers for this request.

A page that can learn its manners

Adaptive sections can compare safe page variations without making the brand feel improvised.

one-columntwo-column

Smart variation only helps if the approved building blocks stay approved.

The site still has a reliable default when the clever bits are taking a break.

Adaptive surface

Test the pitch, keep the guardrails

A governed adaptive block can render a safe default, then learn which approved call to action works better.

experiment: catalog-adaptive-surface-v1strategy: randomstickygoverned

Copy first

The safe version is already on the page before any runtime choice happens.

Reward the better next step

Open roadmap

Build the page that earns its keep

Start with the block catalog, then assemble pages that tell the business story and capture the next lead.

View roadmap
Contract manifest

Programmatic capture coverage

E

Hero

hero

implemented
0.1.0
E

Markdown

markdown

implemented
0.1.0
E

Icon Card Grid

icon-card-grid

implemented
0.1.0
E

Form Template

form-template

implemented
0.1.0
E

Conversion CTA

conversion-cta

implemented
0.1.0
E

Metric Grid

metric-grid

implemented
0.1.0
E

Bento Grid

bento-grid

implemented
0.1.0
E

Product Card

product-card

implemented
0.1.0
E

Product Grid

product-grid

implemented
0.1.0
E

Search Discovery

search-discovery

implemented
0.1.0
E

Integration Embed

integration-embed

implemented
0.1.0
E

Listing Card

listing-card

implemented
0.1.0
E

Listing Grid

listing-grid

implemented
0.1.0
E

Appointment Availability

appointment-availability

implemented
0.1.0
E

Document Intake

document-intake

implemented
0.1.0
E

Estimator Calculator

estimator-calculator

implemented
0.1.0
E

shadcn Showcase

shadcn-showcase

implemented
0.1.0
E

Theme Preview Matrix

theme-preview-matrix

implemented
0.1.0