Step state
Progress can live in memory, session storage, or local storage.
Funnel
Ensemble onboarding funnel
A proof page for page-level funnel configuration and embedded multi-step content.
steps · 3
static fallback
Step 1
Orient the visitor
Start with the promise, the expected outcome, and the smallest next action.
Step 1
Turn a CMS page into a guided app surface.
This page is still just a PageDocument, but page_config tells the runtime to render it as a funnel.
What the funnel controls
LA
Embedded blocks
Each step can contain its own valid block stack.
SI
Event receipts
Step views, completions, and final conversion emit normalized events.
Step 2
Configure the tenant
Collect the operating settings needed to build, cache, or personalize the experience.
conversion
Tenant setup
A future CMS form can capture tenant id, content API URL, theme, and publish target here.
2 fieldsLow-frictionPrivacy aware
We only use your answers for this request.
Configuration surfaces
CMS
Content API
Tenant id and source URI decide what gets fetched at build and runtime.
Theme
Look and feel
Theme JSON controls color, font, scale, and design pattern texture.
Deploy
Distribution
The same config can feed static export, WordPress, or npm runtime usage.
Step 3
Finish with a measurable action
A funnel should make the desired action explicit and analyzable.
Proof points
Configured inside one PageDocument.
Hydrated in WordPress or static app delivery.
Step views and completions use the canonical envelope.
Create a funnel-ready page
This same shape can power onboarding, intake, product fit checks, lead magnets, and sales flows.