Configuring the editor
Wonderpress gives you two levers over what a client can do in the editor: which blocks can be inserted, and which pages can be restructured. Both are declared in code, so they live in the repository and survive every environment.
Curate the inserter
A stock WordPress offers 117 blocks. Once you know which ones the client actually needs, in the theme’s functions.php:
define( 'WONDERPRESS_CURATE_BLOCKS', true );That narrows the inserter to your own blocks plus a small core set: paragraph, heading, list, list-item, image. Adjust the core set with the wonderpress_allowed_core_blocks filter.
This is safe to turn on mid-project. It governs what can be inserted, so pages already built with other blocks keep working.
Lock pages by template
Which pages a client may restructure follows from the page template, declared once:
add_filter( 'wonderpress_template_locks', function () { return array( 'page-landing.php' => 'all', // bespoke, code-rendered: nothing moves 'default' => false, // open composition );} );
Accepted values:
| Value | Effect |
|---|---|
'all' | Nothing moves. No adding, removing, or reordering. |
'insert' | Reorder only. |
false | Open composition. |
'default' covers pages on no particular template. A template you do not name is left exactly as WordPress configured it. Absent is different from false, so the filter cannot accidentally unlock something.
Template manifests can declare the same lock under editor.lock; the manifest sets the default and this PHP filter still wins on the same template key.
Do not use 'contentOnly' here. At the root of the editor, Gutenberg still allows add, remove, and move under that value. Frozen layout with in-place text editing is outside Wonderpress’s v1 editor contract; on locked templates, content is edited through block sidebar controls and ACF fields.
Native editor panels
A template manifest’s editor.native section trims the native chrome per template: blockEditor: false switches the template to the classic screen, and featuredImage: false removes featured-image support there. See Page templates.
The philosophy
The pattern across all of this: a bespoke landing page renders from PHP, hydrates from ACF, and locks 'all', while everyday pages keep an open, curated block editor. The client edits content everywhere, and restructures only where restructuring was designed for.