The WordPress 7.0 Roadmap is into its busy stretch. Beta 2 landed on February 26th, and Beta 3 is scheduled for March 5th. After enough release cycles you learn that the run from Beta to Release Candidate is where things get messy. If your core plugins are not being tested against the latest builds yet, you are behind.
PHP-only block registration
The recent Dev Chat agenda spent a lot of time on PHP-only block registration. For years, shipping even a simple Gutenberg block meant a full Node.js environment and a Webpack config that would break if you looked at it wrong. In 7.0 you can register a block entirely in PHP, which is good for performance and better for whatever sanity you have left.
This does not retire JavaScript. Complex interactivity still needs it. For content-heavy blocks or simple wrappers, though, the refactor drops a pile of legacy overhead and lets you define a block’s attributes and metadata in the server-side registration itself.
<?php
/**
* Simple PHP-only block registration in WordPress 7.0
*/
function bbioon_register_static_block() {
register_block_type( 'bbioon/simple-notice', array(
'title' => __( 'Quick Notice', 'bbioon' ),
'icon' => 'info',
'category' => 'common',
'attributes' => array(
'message' => array(
'type' => 'string',
'default' => 'Maintenance in progress.',
),
),
'render_callback' => 'bbioon_render_notice_block',
) );
}
add_action( 'init', 'bbioon_register_static_block' );The iframed editor and your CSS
The Iframed Editor changes in the WordPress 7.0 Roadmap are going to catch people out. If you have been styling editor components with global CSS, those styles now sit outside the iframe and stop applying. That kills the admin CSS bleed we have fought for years, and it also means you have to load your styles into the iframe context deliberately.
It changes how add_editor_style() behaves too. I have seen dozens of sites where the editor ends up looking like a broken 90s blog because the theme author never accounted for the new wrapper boundaries. My earlier post on how the WordPress 7.0 Iframed Editor affects custom blocks is worth a read before your next deployment.
Tracking the WordPress 7.0 roadmap
The same dev chat covered the restoration of the developer documentation. It sounds minor, but having the official handbook back and synced with Gutenberg 22.6 is a relief. If you are following the WordPress 7.0 Roadmap, watch the bug scrubs that run twice a week. That is where the nasty timing bugs get caught before they reach a client’s live site.
So my advice is to use WP-CLI and spin up a staging site on the Beta branch now. Run wp core update --version=7.0-beta2, then your test suites. Waiting for the general public to find your bugs is not a testing plan.
If the WordPress 7.0 roadmap is eating your dev hours, hand it over to me. I have been wrestling with WordPress since the 4.x days.
What to check before March
WordPress 7.0 pulls blocks away from the JS-only mentality and tightens up the editor’s architecture. The result is cleaner, and it asks more precision of us. Go through your block filters and your editor CSS now, because March is going to move quickly. For where the release stands at the moment, see my breakdown of the WordPress 7.0 AI updates and Beta 2 progress.
