Visual editing without losing the model

3 min

The BetterCMS team Design

Summarize with AI

TL;DR, key takeaways

  • A visual editor is safe when it edits fields, not markup.
  • Give editors the same content two ways in: on the page and in a form.
  • Layout changes belong to sections and variants, not to free-form styling.
  • Review stays honest when it shows what changed in the content, not only the page.

Visual editing is popular for an obvious reason. A writer who can click a headline and retype it does not have to guess which field in which form controls that headline, and does not have to publish twice to find out.

The reason teams end up regretting it is less obvious. A visual editor that lets anyone place anything anywhere is a page builder, and a page builder stores layout decisions as content. Two years later the content cannot be reused because it was never content in the first place.

What is a visual editor?

A visual editor is an editing interface that renders the real page and lets a person change content in place on it. The important word is content. The editor writes back to fields in the model, and the page redraws from the model, so what the writer sees is the same rendering path a visitor gets.

A page builder looks similar and does something different. It stores a tree of boxes and styles, and the words live inside that tree. Both feel like direct manipulation. Only one of them still has usable content when the design changes.

The constraint that makes it work

Every editable region on the page maps to exactly one field on one entry. If a region cannot be traced back to a field, it is not editable. That single rule is what keeps the model intact, and it is also what makes the editor predictable, because there is never a question about where a change went.

  • Text edits write to the field the text came from, and nothing else.
  • A field with no value shows an empty state with the field name, not a gap.
  • Design decisions live in the section, not in the copy.
  • Anything a writer cannot edit is visibly not editable rather than silently ignored.

Give the same content two ways in

Some edits are much easier on the page. Retyping a headline, swapping an image, reordering three sections. Others are much easier in a form. Filling in twelve fields on a new entry, checking that a reference points at the right customer, pasting a long body.

The mistake is picking one. The same entry should be editable both ways, with the two views showing the same values at the same time, so nobody has to leave the tool to do the part it is bad at.

What about layout?

Marketers do need to change layout, and refusing them is how a CMS gets bypassed. The workable middle is a catalogue: developers define the sections, marketers compose pages out of them, and the controls a section exposes are decided when the section is built.

A section might offer a light or dark theme and a choice of two image positions. It does not offer a colour picker. The result is a page that can be rearranged freely and still cannot be made to look wrong.

The question is not whether marketers can change the page. It is which changes are possible at all.

How do you keep review honest?

In-place editing makes changes easy to make and hard to see. A diff of the rendered page is not a diff of the content, and a reviewer scrolling a preview will miss a changed number in a table every time.

So the editor needs a field-level history alongside it. Which fields changed, what they said before, who changed them. That is a small feature that turns a fast editing surface into a safe one.

More articles

View all

Your next website starts here

See BetterCMS running on your pages, not on a sample site.