What Theme Authors Should Know

Theme and pattern authors face new considerations with the default application of contentOnly mode. Patterns reliant on unrestricted editing must be tested to ensure user accessibility aligns with the intended design. Blocks like Buttons, Lists, and Navigation require extra scrutiny due to targeted contentOnly improvements.

What To Do Block Developers: Update block.json files to include "role": "content" for editable blocks. Use "contentRole": true for blocks without content attributes. Implement "listView": true for container blocks. Theme Authors: Audit existing patterns for compatibility with contentOnly mode. Restrict block insertion where appropriate using code or editor settings. Site Admins: Configure disableContentOnlyForUnsyncedPatterns to opt out of default contentOnly behavior where necessary. Plugin Developers: Test plugin functionality against the expanded contentOnly state to ensure UI components render correctly. Related NewsLatest WordPress News & UpdatesSources

Make WordPress Core, 2026-03-15

Report Tag: wordpress core

WordPress Core

WordPress 7.0 Introduces Expanded Pattern Editing Modes

WordPress 7.0 reshapes pattern editing with expanded contentOnly mode, impacting unsynced patterns, template parts, and block development workflows.

Mar 16, 2026 · 4 min read

WordPress Core

Gutenberg 22.7 Introduces New Connectors and Visual Enhancements

Gutenberg 22.7 introduces a new Connectors screen and API, plus visual enhancements like style variation previews, expanding customization and usability.

Mar 12, 2026 · 4 min read