WordPress 7.0 developer features are on the horizon, and it is about time somebody addressed the long-standing bottlenecks in the site editor. Now that 2026 is underway the roadmap for the next major release is taking shape, and while the marketing copy talks about “vision,” the rest of us care about the APIs and the tooling. Gutenberg 22.3 is the release that shows where Core is actually heading.
If you have not filled out the retrospective for the previous version yet, go do it. Plenty of developers complain about regressions after a release when they said nothing during the cycle. Speaking up early is how production sites stay boring.
Responsive grid blocks get real logic instead of a toggle
The Grid block has been one of the block editor’s worst gotchas. You picked either responsive columns in auto mode or a fixed count in manual mode, with nothing in between, so any layout with real complexity ended up as custom CSS fighting the inline styles the editor generated.
Gutenberg 22.3 lets the Minimum column width and Columns controls work at the same time. You set the preferred count and the browser’s CSS Grid engine handles the reflow against the minimum width, so there are no breakpoints left to calculate by hand. The Auto/Manual toggle is gone too, which makes the panel easier to explain to a client and the output easier to predict.
A dedicated screen for fonts
The Font Library is the other one worth calling out. For the last few versions typography settings sat inside the Global Styles UI, about as easy to find as a config file buried in a vendor folder, which made handing a site to a client painful. The latest updates give it a dedicated Appearance → Fonts screen.
PHP-only block registration
I have complained about JavaScript fatigue in the WordPress ecosystem for years. A simple layout block does not need a full React build step. So for me the best of the WordPress 7.0 developer features is the progress on PHP-only block registration: you can register a block with full metadata support and never open a JS file.
<?php
add_action('init', 'bbioon_register_experimental_blocks');
function bbioon_register_experimental_blocks(): void
{
register_block_type('bbioon/custom-logic', [
'title' => __('Logic Block', 'bbioon'),
'icon' => 'admin-settings',
'render_callback' => function($attributes, $content) {
return '<div class="bbioon-block">' . esc_html__('PHP-only output', 'bbioon') . '</div>';
}
]);
}The January 2026 updates read like a platform settling down. Gutenberg’s move fast and break things era is ending, and the APIs are getting standardized enough to build against. Stick to the stable ones and test in the Playground instead of fighting the Core patterns.
