WebBlocks ecosystem

WebBlocks

WebBlocks brings UI patterns, CMS content, documentation, and update workflows into one coherent product system.

Product map showing WebBlocks ecosystem connections between CMS, UI Docs, CMS Docs, blocks, shared slots, media, staged updates, design tokens, and publishing.
Start where the work is

Three entrances, one ecosystem.

The homepage is no longer just a link list. Each destination explains what part of WebBlocks it owns.

WebBlocks CMS

Author content, organize multisite pages, manage media, stage updates, and publish safely.

WebBlocks UI Docs

Use the pattern library behind CMS admin, public rendering, dashboards, forms, and content blocks.

CMS Docs

Read CMS architecture notes, content workflows, release guidance, and operator documentation.

CMS quality you can feel in the workflow.

WebBlocks CMS is designed around maintainable blocks, explicit contracts, and safe publishing paths.

These are product behaviors, not one-off page tricks.

Structured content Native block contracts

Pages are built from discoverable blocks with typed fields, translation ownership, and renderer contracts.

Publishing safety Draft and staged updates

Published pages can be revised in staged drafts before they replace the live route.

Site scope Multisite foundations

Pages, media, navigation, locales, and themes stay scoped to the site they belong to.

Reusable layout Shared slots

Headers, footers, sidebars, and navigation regions can be reused without copying content trees.

Assets Media library

Images, downloads, videos, captions, and metadata remain visible and manageable in CMS records.

Operations System updates

Package-native update workflows align code, schema readiness, cache clears, and release metadata.

Built from the same blocks it promotes.

This homepage can be maintained as CMS content instead of a custom static landing page.

The design maps to native building blocks so editors keep control and developers keep the system clean.

Hero Opening story

Headline, product promise, and primary ecosystem paths.

Grid Product routes

CMS, UI Docs, and CMS Docs become durable content paths.

CTA Next step

Final action remains editable and translation-friendly.

Choose the docs layer you need

Start with CMS, UI Docs, or CMS Docs.

WebBlocks is strongest when the design system, content model, and publishing workflow support each other.