A Content Model Editors Cannot Break

By Simeon Matheka, Founder & Creative Director · Published 2026-09-28 · Updated 2026-09-28 · 13 min read

If the homepage is one HTML blob, every editor can ship a different website. Lock layout, type scale, and the single primary action. Let editors change the headline, the proof, and an image that has alt text.

The homepage looks like the design on Thursday. On Monday it looks like a newsletter. Someone pasted a campaign into the only field the page had, styles and all. The button moved. The type size is whatever the email used. You did not get a new campaign. You got a second website.

Which content management system (CMS) to run, and who is allowed to publish, is the CMS governance guide. This page starts after that choice. The model is the set of fields. If the product cannot express the model, go back to that guide. This page does not set a field cap, a plan tier, or a feature matrix for any product.

The blob is the bug

Framework. A freeform HTML blob is one field that accepts structure, style, and copy at the same time. It feels flexible. It means every editor is a designer and a front-end developer for that page. Blogs can survive a long body, because the template still owns the column, the type, and the header. A homepage, an offer page, and a landing page cannot. Those pages are a composition. The composition has to stay still while the words change.

Structured fields do the opposite. Each slot has a type. A headline is text. Proof is text. An image is a file plus alt text. The template decides where those slots sit. The editor fills them. They cannot paste a table of inline styles into the headline, because the headline field will not take HTML. That constraint is the product. If your CMS only gives you the blob, the constraint has to live in training and in review, which will fail on the week someone is in a hurry. Prefer a model the tool can enforce. If it cannot, say so in the CMS decision, and do not pretend a written policy is a field type.

What stays locked

Three locks. They are design and engineering decisions. An editor should not see a control for them on a marketing page.

• Layout: Which regions exist, in which order, on which breakpoint. A hero, a proof row, a single next step. The editor does not drag a new band onto the page because a campaign arrived. A new band is a design change, with a template change, and then a field if the words must vary.
• Type scale: The sizes, the weights, and the line lengths already chosen. Pasted styles are the usual way this breaks: a span with a font size, a heading level used as a visual hammer, a color that is not in the system. The field stores characters. The template paints them.
• One primary action: One button, one destination, one job for that page. The label can be a field if the words need to change. The fact that there is one action is not a field. A second button is a new page design. Offer pages that stay calm about this are easier to trust. The conversion piece is about that restraint, not about adding more prompts.

The type scale and the components should already exist as a system before they are hard-coded. That handoff is design systems, from brand to code. Design chooses the scale. Development puts it in the template. The content model refuses to reopen it. Who does design versus development, as jobs, is the design and development split.

What an editor may change

Three open slots on a standard marketing page. Add a slot only when you can name what breaks if it is missing, and who reviews it. A page with twenty optional blobs is the blob again, wearing labels.

• Headline: The promise of this page, in the voice you already use. Agree a length in the model as a writing rule, not as a fake product limit. If the CMS does not enforce length, the review does. A headline that wraps into a paragraph is a sign the field is being used as a body.
• Proof: One concrete support for the headline. A permissioned fact, a short quote, a description of the work. Hypothetical numbers do not go here, and neither do numbers nobody measured. If you do not have proof yet, the field stays empty or says what you actually did. Empty is more honest than a trophy you invented.
• Image, with alt: The file and the text alternative are one object. The editor who chooses the picture writes the alt in the same save. Alt states what the image shows when the image is doing work. If the image is decorative, the model has an explicit decorative flag, and alt is empty on purpose. A missing alt on a meaningful image is a failed publish, not a warning you skip.

The owner column is the framework. It is not a permission screen your CMS is guaranteed to show. If the product cannot hide the locked layers, hide them in the template and do not give editors a login that includes the layout builder. A layout builder on the homepage is the blob with a friendlier name.

Three failure modes

These show up the first time someone is in a hurry. Write them into the review checklist so the reviewer is not inventing taste on the day.

1. A blog-post field used for the homepage: The only rich text on the site is the article body, so the homepage reuses it. Editors then paste sections, embed codes, and headings that skip levels. The template cannot tell a campaign line from a 2,000-word post. Give the homepage its own model. Articles keep the long field. Do not point both at one blob and hope the preview saves you.
2. Pasted styles: Copy from a doc, a slide, or an email brings spans, colors, and font sizes. The type scale loses. Strip formatting on paste, or use fields that store plain text. If you need a link inside proof, make that an explicit link field with a label and a destination. Do not accept arbitrary HTML because one sentence needed an anchor.
3. Missing alt: The image uploaded. The alt was optional, so it shipped blank. Anyone who does not see the image gets silence where the proof was supposed to be. Required alt on meaningful images is a publish rule. Decorative is a checkbox with the word decorative, not an empty box people skip.

A fourth failure is quieter. The primary action’s label is edited into a different offer, while the button still goes to the old URL. If the label is a field, the destination is either locked or it is a second field that a reviewer must check. A label that says one thing and a link that does another is worse than a boring button. Review both.

Write the model before the template

Do this on paper or in the CMS schema before anyone themes the homepage. One page type at a time. Homepage first, then the offer page, then the article. Articles are allowed a body. Homepages are not articles.

1. Name the page type: Homepage, offer, article, contact. Each type has its own fields. Sharing a type because it was faster is how the homepage inherits the article body.
2. List locked choices: Layout regions, type scale, the single action and its destination. Write the owner. If the owner is “whoever is logged in,” the lock is already gone.
3. List open fields: Headline, proof, image, alt. Mark required. Mark plain text versus a link. Add a field only with a sentence that starts “the editor must be able to change this without a developer because…”
4. Write the reject list: Raw HTML, pasted styles, a second primary button, a metric you cannot source, an image with no alt and no decorative flag. The reviewer uses this list. Taste is not the list.
5. Match it to the plan: The page exists to do a job you already named. If the model grows a field that does not serve that job, drop the field. Planning the site comes before decorating the schema.

The job of the site, before the fields, is how to plan a website that grows the business. The reason the primary action stays singular is the same restraint as websites that convert without feeling salesy. The model is how that restraint survives an editor who is trying to be helpful.

Hypothetical: the newsletter paste

Hypothetical, labeled as such. A studio needs a campaign line on the homepage for a talk next week. The CMS homepage is one rich text field, the same type as a blog post. The marketer pastes the newsletter. Inline styles come with it. The headline is now a long paragraph. Two links in the paste look like buttons. The template’s real button is still there, so the page has three next steps. Alt text never comes up, because the pasted image did not travel through an image field.

The framework repair is not “be more careful.” The homepage type gets a headline field, a proof field, and an image field with required alt. The campaign line goes in the headline. One sentence of proof goes in the proof field, and only if it is true. The image goes through the image field. The newsletter stays an email. The article body stays on articles. Layout, type, and the single action do not change for this talk. If the talk needs a new section, that is a template change with a named owner, not a paste.

What this model does not decide

It does not pick the CMS. It does not set a price, a user count, or a plugin list. It does not prove the page will convert. It does not replace a design system, and it does not replace a human reviewer for claims. Proof fields still need a person who will reject an invented number. The model only makes that review possible, because the number has a slot you can point at. In a blob, the number is somewhere in the HTML, wearing a font size.

If editors are still designing the homepage from a paste buffer, fix the model as part of the website. Start a conversation with the page types and the field list, not with a theme screenshot.

Tags: content model, CMS, editorial workflow, website planning, design systems