The CMS is for the editor, not the developer

The site nobody could update

I inherited a site once that was, on paper, beautifully built. Clean code, modern stack, the developer clearly proud of it. There was just one problem. Every time the marketing team wanted to change a headline, they had to file a ticket and wait for a developer. The CMS had been built for the person who made it, not the person who had to live with it. A content system only a developer can use isn’t really a content system. It’s a bottleneck with a login.

Design the editor’s day, not the data model

A good CMS is judged by exactly one person: the non-technical someone who logs in on a Tuesday to publish a post. If the fields make sense to them, if they can’t easily break the layout, if they can do their job without asking anyone for help, it works. Everything else, the elegance of the schema, the cleverness of the model, is secondary to that one experience.

• Name fields the way the editor thinks, not the way the database stores them.
• Constrain the layout so a normal edit can’t shatter the design. Freedom the editor didn’t ask for is just a way to break things.
• Watch a real editor use it before you call it done. You’ll learn more in ten minutes of watching than in an hour of guessing.

The measure of a CMS is whether the person who publishes can do it without you in the room.

Guardrails are a kindness

The instinct to give editors total freedom, drag anything anywhere, feels generous and usually backfires. The kinder design is a set of guardrails: rich text that can only produce on-brand type, image fields that crop to the right ratio, components they can arrange but not deform. Constraints aren’t a cage here, they’re what let a non-technical person produce professional results every time. This is the same discipline that keeps a design system alive after the handoff, and it’s one of the real reasons I so often reach for the platforms I do in choosing between Figma, Webflow, and WordPress.

It also decides who holds the power after launch. A store or site the owner can run themselves is the same logic that should drive an ecommerce platform choice: keep the least technical person productive, and you have built something that actually lasts.

What this means for your build

When you set up a content system, design it around the editor’s day, not the developer’s convenience. The site that ships a little less clever but lets the client publish freely will always beat the elegant one that needs a specialist for every change. Getting this right, so a team can actually run its own site, is a lot of what we care about at Dthree Digital. If your current setup makes every small edit a project, that’s worth fixing.