Structured content in the CMS: More freedom for editorial teams

“We just need a quick landing page for the campaign next month.”
Sounds like an easy job. And it is, but only if the CMS is built for it.
In some systems, the editorial team can put together a new page on its own from existing content elements: text, image, teasers, downloads, form – done. In others, every page has a fixed template. If something's missing there, development has to step in first: add a new field, adjust the template, test, deploy.
And just like that, “a quick landing page” turns into a small project.
This is exactly where you see how much freedom a CMS really gives the editorial team.
The more specific the page template, the sooner the exception arrives
Websites are usually thought of in pages. About us. Services. Careers. Landing pages. News. That makes sense. After all, these are exactly the pages visitors see.
So it seems natural to mirror the same structure in the CMS: one model for careers, one for services, one for landing pages. A landing page then gets, for example:
- Title
- Intro
- Image
- three teasers
- Call to action
Works beautifully. As long as the next landing page looks exactly the same.
But for the new campaign, we might need a video. Below it, three matching offers. Then a download. And at the very bottom, a form. So, one more field. One more option. Maybe one more toggle. Bam.
Bit by bit, the tidy page template turns into the form from hell. The real problem: with every template, we're not just mapping what the website needs today. We're also trying to predict what it will look like in two years. And we're astonishingly bad at that.
We'd rather model content than pages

So we prefer to flip things around. Instead of defining what a landing page has to look like, we think about which content elements it can be made of. For example: text, image, teaser, quote, video, download list, contact, form.
Our campaign landing page could then look like this: Text → Video → Teaser → Download → Form
The next landing page, perhaps: Text → Teaser → Teaser → Contact
And the careers page: Text → Benefits → Jobs → Contact
The pages are different. The building blocks are the same.
That shifts a pretty crucial question for the editorial team. It's no longer: “Which page template do I need?” But rather: “What content do I need to tell this story?”
For us, that's the heart of a good editor experience.
More freedom doesn't mean anything goes
Of course, you could simply drop a completely free page builder into the CMS. Font size? Selectable. Spacing? Selectable. Columns? Selectable. Button color? Why not.
That gives you maximum freedom. And, two years later, probably seven different variants of the same teaser.
So our idea of freedom is a different one: Lots of freedom with content. Few unnecessary decisions about design.
That leads to three things we consider especially important for editorial teams.
Editors can put together new pages themselves

Back to our campaign. Nobody foresaw during the relaunch that we'd need exactly this landing page. Nobody has to.
If the elements needed already exist, the editorial team can combine them on its own: Intro → Video → Teaser → Download → Form
No new template. No extra fields. No ticket for development.
For us, that's the most important kind of freedom in a CMS: The website is allowed to change without every change having to go through development first.
Of course, this only works within the existing toolkit. If an interactive 3D product demo is suddenly needed, even a good CMS won't conjure it out of thin air. But many editorial requirements aren't new at all. They're just new combinations of things that already exist. And for exactly that, an editorial team shouldn't need developers.
Learn it once, use it everywhere
Over time, page-based CMSs tend to develop their own little dialects. On one page, a field is called “Intro”. On the next, “Lead”. On the third, “Introduction”. Here you can add three teasers. There, five. On yet another page, you get the same teasers, but somehow they work differently.
Technically, all of that can be explained. Editorially, it's a pain.
Reusable content elements, on the other hand, give the CMS a consistent language. Text is text. Teaser is teaser. Download is download.
Once you've understood how an element works, you can use it anywhere it's intended to go. That cuts down on training. Above all, though, it cuts down on the little everyday questions: “Where was that again?” “Why doesn't this work on this page?” “What's the difference between these two fields?”
A CMS that doesn't keep surprising you is worth quite a lot.
Editors manage content, not pixels
More freedom doesn't automatically mean more options. Often, the opposite is better.
An editor shouldn't have to decide whether two elements need 24 or 32 pixels of spacing between them. Nor should she have to worry about how an element wraps on mobile or which HTML structure is correct for screen readers.
Her decision is: This is a quote. Not: This is 26-pixel text with 48 pixels of spacing on top.
The editorial team takes care of the content. The design system and the website take care of the presentation. So for us, a good editor experience doesn't mean maximum freedom. It means the right freedoms in the right places.
These very guardrails also make the website better

The nice part: what makes working in the CMS easier also helps the website. Structured content gives us clear rules. And we can implement those rules properly, once.
A teaser stays a teaser everywhere
If a teaser is a defined content element, we can set its presentation centrally. If the design changes later, we change the component once. Not every page individually.
The same goes for quotes, downloads, forms or contact blocks. The editorial team can combine the elements in different ways. The website makes sure they still look and work consistently everywhere.
Freedom in how things are put together. Guardrails in how they're presented. That's the deal.
When we know what something is, we can handle it better

A big rich text block can look perfectly clear to a human. Technically, though, it's just text to begin with.
With structured content, we know more. This is an image. This is a job. This is an event. This is an FAQ. This is a download.
And because we know what something is, we can attach rules to it. An image needs alt text, for example. An event can get structured data for search engines. A heading can be slotted cleanly into the page's semantic hierarchy. An element can be built so that keyboard navigation and screen reader behavior are solved correctly, once.
This structure is becoming more interesting for LLMs, too: clearly delimited, semantic content is easier to make sense of than one big wall of markup and text.
So content elements don't automatically make a website SEO-optimized, accessible or AI-friendly. But they give us a place where we can solve these things properly, once. Rather than a little differently on every page.
New requirements expand the toolkit
Of course, sooner or later something comes along that doesn't exist yet. Let's say: a timeline.
Then we build a new content element. We define once:
- what content it needs
- how it's displayed
- how it works on small screens
- which accessibility rules apply
After that, there's a new building block in the CMS: Timeline.
Maybe it was originally built for a single page. But from then on, it's available to the entire editorial team. So a new requirement doesn't just make the next page template more complicated. It expands the toolbox. To us, that's far more sustainable.
Not everything has to be flexible
Now, of course, we could turn this into a rule: Everything is a content element. We wouldn't.
A news article usually has a pretty clear structure. So does a job posting. The same often goes for people, events or products. There, a fixed content model makes sense.
And even on flexible pages, not every paragraph should become its own block. If you have to click “Add text” before every text section, we may have built beautifully structured data, but also a pretty annoying CMS.
So the question isn't: Templates or content elements? It's: Where does the editorial team need structure – and where does it need freedom? That's exactly the line we have to draw anew on every project.
Our simplest CMS test
We have a pretty simple question for this: What happens if the editorial team wants to build a page tomorrow that we haven't planned for today?
For example: “We just need a quick landing page for the campaign next month.”
If the answer is:
«We'll have to build a new template for that first.»
…then the editorial team is only as flexible as our imagination was during the relaunch.
If the answer is:
«The building blocks are already there.»
…we've probably done quite a few things right.
A good CMS doesn't give editorial teams as many options as possible. It gives them the right freedoms. The freedom to recombine content. The freedom to respond to new requirements. And the freedom not to have to deal with breakpoints, HTML structures and pixel spacing.
Then “a quick landing page” might actually be just that.
Quick.

Written by
Josh Wirth
Got a similar challenge on your plate? Let's talk.





