The real cost of a flexible CMS

Headless CMS platforms sell flexibility as a pure win: define any content type, add any field, let non-technical users manage everything themselves. In practice, unlimited flexibility just relocates the hard decisions from the build phase to the day-to-day, and hands them to someone less equipped to make them.

Every field you leave open-ended is a question someone has to answer every time they publish. Every content type you make fully custom is a new way for the site to look inconsistent six months from now, once three different people have added content without a shared sense of the original design intent.

The studios that get this right don't maximize configurability. They figure out which 20% of the content genuinely changes often enough to need a non-technical workflow, and they make everything else deliberately fixed. A rigid template that matches how the business actually operates beats a flexible one that requires taste to use correctly, because taste doesn't scale across a content team.

Which content should be editable, and which should be fixed?

A practical split for most business websites:

Make editable:

• Blog and journal posts.
• Case studies and portfolio items.
• Team members, locations and opening hours.
• Prices, offers and FAQs.
• Headlines and short text on key pages.

Keep fixed in the template:

• Page layouts and section order.
• Navigation structure.
• Colours, fonts and spacing.
• Forms and booking flows.
• SEO settings that should not change by accident, such as canonical tags.

The aim is that someone can publish a post or update a price in minutes, without being able to break the design while doing it.

How do you design content models that stay consistent?

• Use structured fields, not one big text box. A case study with separate fields for client type, problem, solution and result always renders the same way.
• Limit choices. Offer two or three layout options for a section, not a free-form page builder.
• Validate inputs. Character limits for titles and descriptions, required alt text on images, and set image sizes.
• Give sensible defaults, so a new entry looks right even if only the required fields are filled in.
• Write a one-page guide for the people who will publish.

Which CMS should a small business use?

It depends less on the brand of CMS than on how it is set up. Headless options such as Sanity and Payload pair well with fast Next.js sites. WordPress, Shopify and Squarespace have editing built in. For a small team, the best choice is the one where the few things that change often are quick to edit and everything else is protected.

On this site, journal posts are plain Markdown files in the repository, which is the least flexible option there is and exactly enough for how often we publish.

What is the real cost of getting it wrong?

Over-flexible setups lead to inconsistent pages, slower load times from oversized images and embeds, broken layouts on phones, and SEO mistakes such as duplicate titles. Fixing these later usually costs more than designing the right limits at the start.

We set up content models this way on every website redesign and small business website. If you are replacing a site that has drifted, read how to redesign a website without losing your SEO rankings.