8 posts tagged with "gutenberg"

On March 15, 2026, WordPress core published a set of WordPress 7.0 dev notes covering five block-editor changes that matter more than they first appear: pattern editing defaults, viewport-based block visibility, per-block custom CSS, expanded dimensions support, and native text-indent controls.

None of these are headline platform shifts like the Interactivity API or collaboration work. They are more practical than that. They change what editors can do without custom code, what block authors should opt into or opt out of, and where plugin and theme teams can finally stop carrying custom UI or CSS debt.

WordPress officially documented real-time collaboration for the Block Editor on March 10, 2026, during the WordPress 7.0 cycle. This is the first core-facing iteration of Gutenberg Phase 3 collaboration, and it changes how plugin and block code must interact with editor state.

This review focuses on four practical areas: data model, conflict handling, extensibility, and compatibility risk.

As of March 5, 2026, WordPress 7.0 is scheduled for final release on April 9, 2026. The biggest practical shifts for product teams are not headline UI features, but extension-surface changes that alter how plugins should integrate with core.

This review focuses on four concrete areas and what they change for maintainers.

As of February 27, 2026, WordPress 7.0 Beta 2 (released February 26, 2026) is in active testing ahead of the planned final release on April 9, 2026. I reviewed what can break for custom plugins and themes, and built a minimal checklist to reduce upgrade risk.

As of February 24, 2026, WordPress 7.0 is in Beta 1 (released February 20, 2026), and the post editor is planned to run inside an iframe regardless of block apiVersion. If your plugin still depends on top-window DOM selectors, legacy block registration, or unflagged classic meta boxes, this is the migration window to fix compatibility before the planned 7.0 release on April 9, 2026.

WordPress 7.0 Beta 1 is here, and it is not an incremental update. The two big moves are real-time collaboration and native AI integration via the Abilities API. Whether that makes WordPress "an intelligent workspace" or just a more complicated CMS depends entirely on the execution.

I dug into the developer-facing features. Some are genuinely good. Some need caveats.

WordPress offers two distinct preview systems: the Customizer's device preview and the Block Editor's "Preview in new tab" dropdown. Both are extensible, but they require completely different approaches. I dug into both.

I shipped a Drupal 10/11-safe Pathauto delete action because alias cleanup is exactly the kind of workflow that quietly breaks during major-version transitions.