A good editing experience should let someone update the website without feeling that they have been handed the controls to a small aircraft.
It should also let them do enough useful work to avoid asking a developer to move every sentence.
For a custom WordPress theme, that balance comes from deciding which choices belong to the editor and which belong to the design system. Classic templates, structured ACF layouts and block-based editing offer different ways to divide those responsibilities.1 They can also be combined.
The right arrangement depends on the content, the people maintaining it and how much the page structure needs to change.
Choose the editing model around the recurring work
Start with the tasks an editor will perform after launch. Updating opening hours is different from assembling a new campaign page.
Classic templates can suit stable page structures
A template can provide a predictable layout while exposing specific content fields: a heading, introduction, image and contact details, for example.
This can work well when the page’s structure is settled and the team mainly replaces information. Clear fields make the available choices easy to understand.
The tradeoff appears when the business wants a new arrangement. If that requires template development, establish that expectation at handover. A controlled layout is useful when it reflects the actual maintenance needs; it becomes frustrating when everyday changes fall outside it.
Structured ACF sections can provide a useful middle ground
ACF Flexible Content can let editors assemble a page from defined section types. The theme still determines how those sections render.
A business might have approved options for a text-and-image section, a project gallery and a call to action. Editors can select appropriate sections and supply the content, with controlled variations where they add value.
This approach needs thoughtful field design. Labels, instructions, sensible defaults and limits on unsuitable combinations are part of the implementation. A list of thirty vaguely named layouts is technically flexible and emotionally quite a lot.
It is also important to distinguish data from presentation. A testimonial’s author and quotation are content. The spacing around every testimonial may be a shared theme decision.
Custom WordPress themes are our bread and butter. See our WordPress services.
Blocks can offer direct composition with appropriate constraints
The block editor provides a more visual environment for creating content. A custom theme can curate the available blocks, patterns and settings, while custom blocks supply business-specific components.
ACF Blocks can be part of that approach. ACF’s January 2026 review describes its Blocks V3 and opt-in inline editing work. Those capabilities depend on the relevant versions and how the developer implements the blocks; installing ACF does not make every custom field editable directly in a page preview.
Block-based editing still benefits from a clear design system. Approved typography, color choices and component variations can provide useful freedom without making every page a fresh branding experiment.
| Often suits | Watch for | |
|---|---|---|
| Classic templates | A settled page structure where the team mainly replaces information | New arrangements need template development |
| ACF Flexible Content | Pages assembled from approved section types while the theme keeps the design | Labels, instructions, sensible defaults and limits need careful field design |
| Blocks | More visual, direct composition within a curated set of options | Still needs a clear design system for typography, color and spacing |
Define the choices, then prove them with real content
Once the editing model is chosen, review what people can actually change and what each choice affects.
Make local and shared changes distinguishable
An editor should understand whether they are changing one page, a reusable component or a global setting. Similar-looking controls can have very different consequences.
For example, changing the text on one call-to-action section is a local content decision. Changing the theme’s primary button style may affect the whole website. Those actions should not feel indistinguishable in the interface.
Worth reading next: A custom WordPress theme needs a small design system.
Theme.json can help define shared settings and styles in appropriate themes. Custom components need to use those values deliberately. Other theme architectures may use their own controlled settings, with the same need for understandable scope.
Content controls and editor locks should also be distinguished from security permissions. Restricting a layout option helps maintain consistency; the application still needs appropriate access control for actions and data.
Review the difficult content, not only the demonstration page
Try a long heading, an absent optional image, several repeatable items and a link with a descriptive label. Preview the result at smaller widths.
Then ask an intended editor to make a realistic update using the supplied instructions. Watch where they hesitate. A field name that makes perfect sense to its developer may be considerably less welcoming to someone thinking about tomorrow’s promotion.
Include the ordinary recovery route. Can the editor preview a change, correct a mistake and understand how revisions or publishing work in this particular setup? Explain any limitations rather than letting the first live update become the training session.
I would choose the model that makes the team’s recurring work comfortable, then reserve specialist decisions for the people responsible for the theme. A hybrid arrangement is often worth considering when different content types have different needs.
The handover should leave people confident about their useful choices. They can update the site, see what they are doing and recognize when a larger change needs help. That is a much nicer relationship with a website than wondering which innocent-looking field deploys the emergency parachute.