Source
Structured payload
SEO, hero, sections and CTAs live in a JSON contract per page, not in hidden route files.
CAPABILITY / WEB BUILDER
Multi-brand sites with structured contracts, audit gates and visible publication state.
Web Builder is the capability of the platform that handles public surfaces. Pages are structured payloads, not files. Blocks are shared and brand-aware. The publication loop runs through audits before public action. This site is built with it.
WHAT IT DOES
The capability owns the path from page intent to public surface.
Web Builder is opinionated about what a productive page looks like: structured source, thin render, audited gate, owner-approved publication, readback after action.
web-builder / production route
Canonical route /platform/web-builder/
Surface state live capability
Structured source Page intent, SEO, hero, sections and CTAs live in an auditable payload.
ready
Thin render Astro routes render shared blocks; no strategy hidden in route files.
ready
Audit gate audit:platform must pass before public action. Sitemap, hreflang, structured pages, slug uniqueness — all checked.
required
Brand contract Each site validates against a zod brand schema. Cross-brand consistency is enforced, not aspirational.
ready
Public action Deploy, DNS and indexability are owner decisions, not pipeline auto-applies.
blocked
Publication gate owner approval
The capability prepares the surface; the operator approves the public action.
INTERACTION LADDER
Static by default. State only when the visitor needs it.
The capability defaults to static rendering. Interaction is added when the visitor changes a scenario, compares states, or checks a readiness — not as decoration.
Layer output
HTML-first
Most proof is readable as HTML: route, source, gate, owner, readback. If the static surface cannot explain the idea, interaction will not fix it.
- SEO-readable
- Local assets
- No provider dependency
Layer output
Tiny JavaScript when meaningful
Progressive enhancement only when the visitor changes a scenario or reveals a state that would be worse as duplicated copy.
- Readable before JS
- No framework dependency
- Audited like everything else
Layer output
Generated visuals when they carry proof
A static SVG, diagram or generated visual belongs in the site when it makes the operating layer clearer than another paragraph.
- Owned by the repo
- No remote embeds
- Compressed and auditable
WHAT IT POWERS
Page templates with clear readiness shape.
Web Builder ships a small set of page types. Each has a defined contract, audited readiness, and owner gates.
Service pages
For a defined offer with scope, objections, proof and contact path. Structured contract. Audited before release.
Capability pages
Like this one. For a platform capability with operating proof, what-it-does, how-it-works and activation path.
Solution pages
For a vertical combination of capabilities + services. Audience-led structure.
Editorial articles
For long-form content with TOC, reading progress, related posts, author bio. Article UX kit included.
SHOWCASE — KIT IN USE
Six surfaces demonstrating the kit on real sections.
The capability description is one thing; seeing the kit run is another. The showcase splits the kit into six categories — templates, heroes, proof blocks, marketing flagship, article UX, motion patterns — and each surface renders the blocks inline, not described.
Templates
The 5 page templates this site is built with — service, capability, solution, article, hub.
Heroes
Centered · split · cinematic with motion (ken-burns, parallax, gradient-overlay). All 6 variants demonstrated.
Proof blocks
SystemProofPanel · OperatingBridge · LayeredSystem · CapabilityBento · ReadinessMatrix · IntegrationContext · ProcessSteps.
Marketing flagship
TabsSection · CaseStudyCard · Reviews carousel · PricingTable · CodeBlock · Tooltip · AnnouncementBar.
Article UX
TableOfContents · ReadingProgress · AuthorBio · RelatedArticles · ArticleShare · InlineNewsletterForm.
Motion patterns
AnimateOnScroll variants · GradientBlob · hover-effects utility classes · Hero motion (cross-linked).
ACTIVATED THROUGH SERVICES
Which services run on this capability.
The capability ships the kit, the contracts, the audit gates and the publication loop. The services define what the site exists to do and how it operates inside a client engagement.
Web architecture
Site architecture decisions — taxonomy, route map, content contracts, audit gates — for sites that need to scale.
Lead systems
The capture-and-CRM layer built on the kit: forms, qualification, routing, follow-up audit.
GEO content
Editorial surfaces with structured contracts, FAQ entity Q&A, taxonomy aggregation — all running on the kit.
USED IN VERTICALS
Which solutions use this capability.
Traditional SMEs
B2B SMEs that need a site engineered for organic discovery, not just a brochure with a contact form.
Strategic partners
Multi-brand portfolios where the kit handles brand-aware tokens, structured contracts and cross-brand consistency.
ACTIVATE
If your operation needs sites that scale with audited gates instead of brittle one-offs, this capability is the starting point.
Web Builder activates through an engagement: brand contract, structured contracts, audit gates, publication loop. The conversation starts with the current friction.
Talk about activation