Content control, not design control

Every website tool that lets a client edit their own site makes the same trade, and almost nobody names it: to let them change the words, it lets them change the layout.

That trade is invisible while you're building, because you're the one holding the tool and you want both. It becomes visible about three weeks after handover.

The shape of the problem

A client opens their site to add an event. The events section has three columns. They add a fourth item, and the section reflows into something that was never designed. On a phone it's unreadable. They don't notice, because they were looking at a desktop and checking the date was right.

They did nothing wrong. They added an event, which is what the site was for. The tool let them do something else at the same time.

This isn't solved by training. You can explain the grid, write a handover document, record a Loom. It works for about a month. The tool is still a design tool, and a design tool's job is to let you design.

Permissions don't fix it either

The usual answer is a restricted editing mode — lock the layout, hide the style controls, give the client a simplified view. It helps, and it's better than nothing.

But it's a layer on top of a system that still thinks in pages and boxes. The constraint is a setting, which means it can be wrong, incomplete, or quietly bypassed. And every new section someone builds is a new set of controls that need locking. You're maintaining a fence.

The structural version

The alternative is to make the constraint a property of how the site is built rather than a permission on top of it.

You define a content model: what a Page is, what sections it can contain, what fields each section has. The editor the client sees is generated from that model. If the model says a feature grid has three slots, the client's editor has three slots. There's no fourth to add — not disabled, not hidden behind a permission. Absent.

The rule that follows is short enough to hold in your head: if it's in the model, they can change it. If it isn't, they can't.

What that buys

The client gets genuinely unlimited freedom in the dimension they actually care about. Eighth event, ninth post, new location, new team member, at midnight, without asking you. That freedom is real and it's the point — this isn't about restricting clients, it's about restricting the wrong axis.

And you stop being the person who gets called when their site looks wrong on a phone, because there is no arrangement of their content that looks wrong on a phone.

What it costs

You have to decide the sections up front. A client can't invent a new kind of section, which means when they want one they come back to you — and that's billable work rather than an unbilled repair.

It also means the tool is worse for building your own site, where you do want both kinds of control. That's a trade we make deliberately.

The line

Most of the argument about client-editable websites is about how much freedom to give. We think that's the wrong question. The useful question is which freedom — and the answer is: all of the content, none of the design.