The bargain every website platform offers
Every platform makes the same trade, whether it says so out loud or not. Use our themes. Build with our blocks. Stay inside our page builder. Design the way our tool wants you to design. In exchange, you get a website.
For a great many sites that trade is perfectly reasonable. It stops being reasonable at a specific moment, which is when the design you actually want cannot be expressed in the vocabulary the tool provides, and somebody has to decide which one gives way. The design always does, because the tool cannot.
The method is deliberately platform-agnostic
The part of the protocol that does the thinking has no idea what runs underneath it. Reading a design, classifying its structure, typing its editable regions and producing clean output are all operations on markup and styles. None of them require knowing which content platform will eventually store the result. Only a thin final layer, the part that speaks a specific platform’s way of holding content and rendering pages, is platform-specific. That layer is written once per platform and then reused indefinitely.
That architecture is a deliberate bet. Content platforms rise and fall on a cycle measured in years, and a method welded to one of them inherits its lifespan. A method that treats the platform as an interchangeable final step outlives any particular one.
Where the protocol runs today
WordPress is proven and production-ready. That matters on two counts: roughly two in five websites run on it, and its typical bloat makes the improvement dramatic rather than marginal. You can confirm what the output looks like in seconds by viewing the source of any page it produces.
Drupal is the natural next home, since its native concept of structured entities and fields is close to how the protocol already thinks. Every major platform after that follows the same pattern: one focused effort to teach the protocol that platform’s language, after which everything upstream simply works. We name the platforms precisely because the whole argument rests on claims anyone can check.
The real cost of the bargain, and what refusing buys
The visible cost is aesthetic, though the invisible ones run larger. Design decisions get rounded toward whatever the tool supports natively, while the tool leaves its machinery behind in every page it renders. The team is locked into one vendor’s format, so changing tools later means rebuilding rather than migrating. And a design that cannot be maintained without a developer stops being maintained at all. Refusing the trade returns four things.
The design that launches is the design that was drawn
No rounding toward what the tool supports natively. The composition that left the designer’s hands is the composition a visitor sees.
A document written the way a careful developer would write it
Produced automatically, on every page. What that means in specifics is covered in clean semantic markup.
The content platform your team already knows
Nobody learns a new tool, and no developer is required for routine changes. The editing experience is covered in familiar CMS backend.
A design source that can change entirely
Swap the model, the agency or the tool that produced the design, and nothing downstream breaks.
Bringing a design from anywhere
The ingestion contract is narrow on purpose, which is precisely what makes it broad in practice. Markup and styles go in. A working pattern library comes out. Generated by a language model, drawn by an agency, exported from a design tool, or hand-coded by somebody who thinks in CSS. The protocol does not care, and that indifference is the point.
"A pipeline that only accepts one origin has quietly bought a share of every future decision a team makes about tooling."
The specific path for AI-generated designs is covered in AI design import, and the manifest that describes a classified design is covered in composer blueprints.
Where the protocol connects
The document the protocol emits is covered in clean semantic markup, what it deliberately leaves out in zero CSS bloat, the measured result in faster page speed, and the media pipeline in aggregated assets. The design freedom this creates is covered in unconstrained front end, and the editing experience that survives it in familiar CMS backend.
How the engagement runs
Protocol work happens through screen shared working sessions, and the first thing we usually do is run your existing site through an analysis so you can see the difference rather than take our word for it. If you have accepted a compromise on your design because a platform could not express it, that compromise was never necessary.