Creative Freedom Without Brand Chaos: Designing a Better CMS

Overview

Most editors are not trying to design a website from scratch. They need enough control to publish content properly, while the CMS takes care of the decisions that should stay consistent across the site.

Building a visual layout involves far more than arranging content on a page. Designers need to decide on spacing, typography, colours, container widths and how each component adapts across different screen sizes. Those decisions quickly add up.

This level of control may look like flexibility, but it can quickly become another job. Editors are usually trying to add a case study, update a service, create a landing page or publish an Insight. The CMS should help them do that confidently, without expecting them to revisit decisions already made during the original design and development process.

More options do not automatically make a CMS more useful. A better CMS gives editors the right choices while handling the decisions they should not need to think about.

Why unlimited flexibility often creates worse websites

Complete flexibility can be appealing at the start of a project. A client may reasonably ask to control colours, spacing, layouts, typography and alignment. Nobody wants to feel restricted by their own website, particularly if they have previously worked with a CMS that made even simple changes difficult.

The problem is that every additional option creates another decision. An unrestricted CMS can leave editors responsible for choices such as:

• how much space to leave between sections
• which heading treatment to use
• whether a colour combination has enough contrast
• how wide a section should be
• how a layout should respond on smaller screens

When a website gives editors unrestricted control over layout and styling, it also gives them responsibility for keeping those choices consistent. One editor may use generous spacing between sections, while another prefers a tighter layout. Someone else may introduce a different background colour or heading treatment because it works on one particular page.

None of those decisions may look serious on their own, but over time they add up. Similar pages begin to behave differently, new team members have to work out which options are safe to use and existing pages become harder to update because nobody is quite sure whether a choice was intentional.

The issue is not that editors are making bad decisions. It is that the CMS is asking them to make decisions that should already have been resolved by the design system.

Useful choice is different from unnecessary choice

Good editing systems still provide freedom. The useful distinction is between decisions about the content and decisions about the underlying design.

An editor may need to decide whether related content should appear as cards, a list or a grid because that affects how much is shown and how easily people can compare it. They are less likely to need control over the exact number of pixels between each item. They may also need to choose whether a section should feel neutral, prominent or visually distinct, but that does not require an unrestricted colour picker.

These decisions fall into three groups.

Useful choices

Decisions that affect the content or how it should be communicated, such as:

• choosing how related content should be presented
• selecting featured content
• deciding whether an image is needed
• choosing between approved section treatments

Unnecessary choices

Low-level design decisions that editors should not need to make repeatedly, such as:

• entering arbitrary spacing values
• creating new colours
• setting individual responsive breakpoints
• manually correcting the width of nested content

Automated decisions

Rules the CMS can handle based on the component and its context, such as:

• applying the correct spacing
• adjusting a grid for smaller screens
• preventing duplicated padding
• using the appropriate content width

A well-designed CMS keeps useful decisions visible and handles the lower-level details in the background. Editors retain flexibility where it genuinely helps them communicate, without being asked to manage the design system themselves.

Turning the design system into editing controls

A design system should not exist only in a design file or within the front-end code. If a website has agreed rules for colour, typography, spacing, layout and component behaviour, those rules should also shape the editing experience.

In WordPress, this can be reflected through a controlled colour palette, approved text styles, defined content widths and purpose-built Gutenberg blocks. Instead of choosing any possible colour, editors choose from combinations defined within the website’s design system. Instead of building a layout from unrelated elements, they use a block created for that type of content. Instead of manually adding space until a section looks right, the component handles it consistently.

This creates a straightforward relationship between the design system and the published website:

How purpose-built blocks give editors useful freedom

Reusable Gutenberg blocks allow editors to create varied pages without starting from nothing. A website may include blocks for cards, testimonials, calls to action, statistics, related content, service listings, image and text layouts or process diagrams.

Each block can offer controls relevant to its purpose. A card block might allow an editor to choose the number of columns or whether an image is shown. A testimonial block might offer different approved layouts. A listing block may allow content to be selected manually or generated from existing WordPress content.

The editor is still making decisions, but they are about the content and how it should be communicated. The underlying rules for spacing, alignment, typography and responsive behaviour remain consistent. Editors gain freedom through combining useful components rather than configuring every visual detail from scratch.

Different content needs different levels of flexibility

Not every part of a website needs the same level of flexibility. Some types of content benefit from a stable structure, while others need more room to vary.

An article, for example, may always need a title, author, publication date, category, introduction and related content. A case study may need consistent project information, outcomes and service references. These elements can be placed or generated automatically, making publishing quicker and reducing the chance of important information being missed.

The main content area can still remain flexible. An editor may use images, quotes, statistics, columns or other blocks within the article while the wider structure stays consistent. Campaign pages and landing pages may need a broader choice of approved layouts because their communication requirements vary more.

The right approach depends on the purpose of the content:

• Structured content, such as articles and case studies, benefits from consistent surrounding elements.
• Flexible content, such as campaign and landing pages, may need a wider choice of approved layouts.
• Shared components, such as calls to action and listings, should behave consistently wherever they are used.

The aim is to keep repeated information consistent while allowing more freedom where the content genuinely needs it. A good CMS does not apply the same restriction everywhere; it responds to the purpose of the content.

Good defaults remove unnecessary work

Some of the most useful parts of a CMS are the decisions an editor never has to make. A block can adjust its spacing when placed inside another section, a card layout can adapt when fewer items are selected and nested blocks can avoid doubling the padding around them.

Without sensible defaults, editors have to correct the same minor layout problems repeatedly. When the system understands the context in which a component is used, those problems can be prevented rather than fixed afterwards. This makes the website easier to manage and preserves consistency without adding more controls.

Constraints can support accessibility

Editing controls can also help to prevent some common accessibility problems. Editors can choose from colour combinations that have already been checked for contrast, rather than creating their own. Text styles keep headings and body copy at sensible sizes, while familiar components make the site easier to use from one page to the next.

This does not mean a structured CMS automatically makes a website accessible. Accessibility still depends on the quality of the design, development, content and testing. Editors can still add unclear link text, poor heading structures or unsuitable alternative text.

The CMS can, however, remove some avoidable risks by guiding editors towards suitable choices and making inappropriate ones harder to introduce accidentally. That is more useful than expecting everyone who updates the website to understand every design and accessibility decision behind it.

The editor experience is part of the website

Why this matters years after launch

The long-term effect of these decisions matters more than how impressive the CMS looks during its initial demonstration. Websites are managed by different people over several years. Teams change, new sections are added and the reasons behind particular design decisions are gradually forgotten.

A completely open system depends on every future editor knowing how the original design was meant to work. Putting some controls in place reduces that reliance and brings three practical benefits.

New team members can also learn the website more quickly because the available choices are clearer. Changes to the design system can be applied across multiple parts of the site without losing the consistency that made the original design work.

A better CMS makes the right decisions easier

A good CMS gives editors control where they need it, while keeping design and technical decisions within the system.

The right balance will vary between organisations and types of content. Editors should have enough freedom to communicate clearly and create pages that suit their purpose, without having to recreate the design system each time they publish something new.

Creative freedom does not require a blank canvas. It comes from useful choices, sensible defaults and a system that supports consistency without getting in the way.

How we can help