WordPress 7.0 development is hitting the home stretch, but the headline this month isn’t what’s in the release. It’s what just got pulled. If you’ve been following the “Armstrong” release, you know the team was betting big on real-time collaboration (RTC). After a run of recurring bugs and race conditions, the core team pulled it. That’s the right call. Shipping a stable platform beats shipping a broken gimmick.
The RTC reality check in WordPress 7.0 development
Pulling a flagship feature 12 days before a major release is messy. The concerns were around surface area, server load, and memory efficiency, and they were enough to make the core team backtrack. I’ve spent enough time debugging race conditions in custom WooCommerce checkouts to know that “nearly ready” usually means “breaks under load.” If you’ve already started building plugins that lean on the Presence API for RTC, you’ll need to pivot. WordPress 7.0 now ships on May 20, 2026, as a stability-first release.
For more on the fallout, read about why stability trumps new features in the current RC3 cycle. The delay gives the native AI infrastructure and the new DataViews-powered dashboard the performance headroom they need.
Content types system: the architect’s long game
While RTC is out, work on a native “content types” system is finally taking shape. It’s been requested since the WordPress 3.0 days, when Custom Post Types (CPTs) first arrived. The current Gutenberg experiment is a longer-horizon goal for WordPress 7.0 development and beyond. The aim is a UI-driven way to manage data structures that we’ve historically had to handle through register_post_type() in a functions.php file.
The new @wordpress/grid package
The big technical addition this month is the @wordpress/grid package. It’s more than another styling utility: it gives you a standardized toolset for building grid-based interfaces inside the editor. If you’re building complex plugin UIs, keep an eye on it. It makes tiles and layouts behave consistently, especially when they span multiple rows.
HEIC conversions and capability gating
On the “boring but essential” front, there’s a fix for HEIC-to-JPEG conversions. Before this, when a client uploaded a HEIC image from an iPhone, the client-side conversion kept the .heic extension even after turning the file into a JPG. That broke server-side scripts and CDNs that expected standard mime types. WordPress 7.0 development finally corrects it to use the .jpg extension.
There’s also a new security layer for per-block custom CSS. Users without the edit_css capability will no longer have their block-level CSS preserved on save. That closes a possible exploit where a contributor could bypass global CSS restrictions. Here’s how I’ve been handling capability checks for custom block features lately:
<?php
/**
* Example of capability gating for custom block attributes.
* Prefixing with bbioon_ for safety.
*/
function bbioon_gate_block_css_capability( $content, $block ) {
if ( ! current_user_can( 'edit_css' ) && isset( $block['attrs']['customCSS'] ) ) {
// Log the attempt or strip the attribute
unset( $block['attrs']['customCSS'] );
}
return $content;
}
add_filter( 'render_block', 'bbioon_gate_block_css_capability', 10, 2 );
Theme polish: tabs and accordions
The Tabs block, still an experiment, got a round of polish this month. It now aligns with WCAG patterns for clearer semantics, and the top-level structure is locked so users can’t accidentally delete the required wrapper blocks. That gives theme developers a more stable DOM to write CSS overrides against.
If this WordPress 7.0 development work is eating up your dev hours, I can take it on. I’ve been wrestling with WordPress since the 4.x days, and I know where the bottlenecks hide.
The road ahead for May 2026
The bigger lesson from WordPress 7.0 development is that architectural integrity beats marketing deadlines. Pulling RTC was painful but necessary. For those of us building on the platform, attention now moves to the AI Client, the content types system, and the refined Gutenberg design tools. If you haven’t tested your themes against RC3 yet, you’re behind. Use the WordPress Playground to spin up a nightly build and start breaking things before May 20.
