I once handed over a carefully designed website to a client, with a consistent colour palette, a clear type scale and well-spaced layouts. Three months later, I visited the blog. One post had bright green headings. Another used five different font sizes in the same paragraph. A landing page had a cover block with white text on a pale yellow background, completely unreadable. None of this was malicious. The editors were simply using the options the editor gave them. The answer is to curate the block editor rather than abandon it.
The block editor is designed to be flexible enough for every kind of site. On a client project, that flexibility is often more than editors need and more than the design can survive. The answer isn’t to take the block editor away. It’s to curate the block editor: remove options that don’t belong, lock what shouldn’t change and provide ready-made building blocks for common needs. Done well, editors find the editor easier, not more restrictive, because the choices they see all lead to good results.
Start with theme.json
For block themes and classic themes that support it, theme.json is the most powerful curation tool. It controls which design options appear in the editor.
Colours
Limit colours to the brand palette and remove the custom colour picker:
Editors then see only approved colours, and none of the dozens of defaults that WordPress offers otherwise.
Typography
Limit font sizes to a defined scale and remove custom sizes:
Removing letter spacing, decoration and style controls takes away options most editors rarely need and frequently misuse.
Spacing, borders and layout
You can disable custom padding, margins, borders and other controls, or limit spacing to a preset scale. Defining spacing presets keeps layouts consistent while still allowing editors to adjust spacing within the system.
Per-block settings
theme.json also supports settings for individual blocks. You might allow background colours on Group blocks for section styling but disable them on Paragraph blocks:
That kind of targeted curation prevents the most common design mistakes without removing useful features.
Limit which blocks are available
The editor offers many blocks most client sites never use: verse, preformatted, RSS, tag cloud, archives, calendar, page list and others. Each one is another choice for editors to wonder about.
Restrict the inserter with the allowed_block_types_all filter:
Allowing different blocks per post type is often the right approach. Blog posts need content blocks. Landing pages might also need columns, cover and media and text.
Be careful to include child blocks, like core/list-item and core/button, and core/pattern if you use synced patterns. Removing them breaks their parent blocks.
Remove unwanted block styles and variations
Some core blocks include styles or variations that don’t fit your design, like rounded images or outline buttons. Remove them with a small editor script:
Provide patterns for common layouts
Restriction alone can frustrate editors. The other half of curation is giving them ready-made building blocks for the things they actually create: a call-to-action section, a testimonial, a two-column feature, a team member card, a FAQ section.
Register patterns in your theme’s patterns folder or with register_block_pattern. Organise them into clear categories named after what editors are trying to do. When an editor can insert “Call to action, dark” and simply change the text, they get a professional result in seconds.
Synced patterns, formerly reusable blocks, are useful for content that should be identical everywhere, such as a standard disclaimer or contact box. Changes to a synced pattern update every instance.
Lock what shouldn’t change
Block locking prevents editors from moving or removing specific blocks. In a pattern or template, add lock attributes:
Content-only locking goes further. A group with templateLock set to contentOnly lets editors change text and images but hides the structure, so they can’t add, move or delete blocks inside it or change design settings. That’s ideal for structured sections like a hero, pricing table or team grid, where the layout must stay intact but the words need updating.
In block themes, templates themselves can be locked so editors work only in the content area.
Tailor by role
Not every user needs the same editor. Administrators and the agency may need full control; content editors need less. Several approaches help:
- Filter allowed blocks based on the current user’s role.
- Restrict access to the Site Editor to administrators only, so content editors can’t accidentally modify the header or templates.
- Use the block_editor_settings_all filter to adjust settings, such as disabling the code editor for certain roles.
- Disable the block directory, which lets users install new blocks from the editor, with remove_action on the relevant hook or by limiting plugin installation capabilities.
Keep the content area familiar
A curated editor should still feel like WordPress. Avoid hiding so much that editors can’t find standard features they’ve used on other sites. The goal is to remove options that lead to inconsistency, not to create an unfamiliar tool.
Document and train
Even a well-curated editor benefits from a short guide. Create a page on the site, or a short video, showing:
- How to insert each pattern and when to use it
- Which colours and sizes mean what, such as “Large is for introductions”
- How to add images properly, including alt text
- Who to contact when they need something the editor doesn’t allow
Editors who understand why options were curated are much more likely to work within the system than around it.
Review after launch
After a few months, look at how editors are using the site. Which patterns are popular? What did they try to do that the editor didn’t allow? Are any design problems still appearing? Adjust the curation based on real use. Curating the block editor is an ongoing conversation, not a one-time lock-down.
A real example: an editorial team of twelve
A publishing client had twelve editors of varying experience producing several articles a day. Before curation, almost every article needed a final design pass by a senior editor to fix colours, inconsistent spacing and oddly sized headings. After we limited colours to five brand swatches, restricted font sizes to a three-step scale, trimmed the block inserter to fifteen blocks for posts and provided eight patterns for recurring elements like pull quotes, info boxes and author notes, the design pass became unnecessary. Articles were consistent from the first draft.
Interestingly, the editors were happier too. Several said the editor felt simpler and less intimidating. The options they lost were ones they had never wanted to think about; the patterns they gained solved problems they faced every day.
Plugins add blocks too
Every plugin that registers blocks adds to the inserter. Form plugins, SEO plugins, WooCommerce, slider plugins and block libraries can add dozens. Include plugin blocks in your curation: allow the ones editors need, hide the rest. Some block libraries let you disable individual blocks in their settings, which also stops their assets from loading.
Balance control and trust
Curation works best when it reflects trust rather than suspicion. Explain to clients that limits protect the design they paid for and make editing faster. Leave clear routes for requests, so when an editor genuinely needs something new, such as another pattern or colour, it can be added properly. A curated editor that evolves with the client’s needs stays useful for years.
Test with a real editor account
Before handover, log in with an editor account, not an administrator, and create a typical page from scratch. You’ll quickly notice anything missing, such as a pattern editors need, or options still visible that should be hidden. Ten minutes of testing as the client saves many support emails later.
Revisit after WordPress updates
Major WordPress releases add new blocks, design tools and settings. Some appear in the editor automatically, unless your curation already restricts them. After each major release, review the editor as a content editor would and decide whether the new options belong in your curated set or should be hidden.
Keep a record of decisions
Note why each option was removed or locked. When a future developer or the client asks why something isn’t available, the reasoning is already written down.
Frequently asked questions
Will curating the editor stop clients from editing their site?
No. It removes options that cause design inconsistencies while keeping full control over content. Most clients find it easier to use.
Do these settings work with classic themes?
Many theme.json settings work in classic themes that include a theme.json file. Block allowlists, locking and patterns work everywhere the block editor is used.
Can administrators still use all options?
Yes, if you apply restrictions by role or post type. Administrators can keep full access while editors see a simpler interface.
What about page builders?
Page builders have their own settings for limiting widgets, colours and fonts. The principles are the same: limit choices to the design system and provide templates.
