One architecture across layers
The ecosystem is meant to stop the drift between source structure, design implementation, and CMS delivery.
WebBlocks ecosystem
A layered system for teams that want structure first, then design, then CMS delivery.
WebBlocks defines the structural model. WebBlocks UI applies the default design language. WebBlocks Craft brings the same system into Craft CMS. The public site treats them as one connected stack so teams can move from source markup to published implementation without switching mental models.
HTML-first
Static-friendly
Server-rendered
Source-visible
Core system
WebBlocks
->Use the structural layer to define clear markup, reusable blocks, and a predictable model that other layers can consume.
Design layerWebBlocks UI
->Apply the default design language with token-based CSS, layout shells, components, icons, and minimal JavaScript.
Craft integrationWebBlocks Craft
->Carry the same model into Craft CMS so content modeling, rendering, and editorial flows stay aligned with the frontend system.
Read the source, not the abstraction
Everything stays close to explicit HTML, readable CSS, and inspectable behavior so the final output remains understandable.
Server-rendered and static-first teams
It fits products built with Twig, Blade, ERB, Django templates, plain HTML, and other systems that value direct markup.
How the layers connect in practice
Start with the structural system, apply the default presentation layer, then carry the same model into your CMS integration without inventing a second product architecture.