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 yanked. If you’ve been following the track for the “Armstrong” release, you know the team was betting big on real-time collaboration (RTC). However, after a series of recurring bugs and race conditions, the decision was made to pull it. This is exactly the kind of move a senior dev appreciates; it’s better to ship a stable platform than a broken gimmick.
The RTC Reality Check in WordPress 7.0 Development
Pulling a flagship feature 12 days before a major release is messy. Specifically, concerns around surface area, server load, and memory efficiency forced the core team to backtrack. I’ve spent enough time debugging race conditions in custom WooCommerce checkouts to know that “nearly ready” is usually code for “breaks under load.” If you’ve already started building plugins that rely on the Presence API for RTC, you’ll need to pivot. WordPress 7.0 will now ship on May 20, 2026, as a stability-first release.
For more context on the fallout of this decision, you should read about why stability trumps new features in the current RC3 cycle. This delay ensures that the native AI infrastructure and the new DataViews-powered dashboard have the performance headroom they need.
Content Types System: The Architect’s Long Game
While RTC is out, the work on a native “Content Types” system is finally taking shape. This has been a long-requested feature since the WordPress 3.0 days when Custom Post Types (CPTs) first arrived. The current experiment in Gutenberg represents a longer-horizon goal for WordPress 7.0 development and beyond. It’s aiming to provide a UI-driven way to manage data structures that we’ve historically been forced to handle via register_post_type() in a functions.php file.
The New @wordpress/grid Package
A major technical addition this month is the @wordpress/grid package. This isn’t just another styling utility; it’s a standardized toolset for building grid-based interfaces within the editor. Furthermore, if you are building complex plugin UIs, this is a transient you should be tracking. It brings consistency to how tiles and layouts behave, especially when spanning multiple rows.
HEIC Conversions and Capability Gating
On the “boring but essential” front, there’s a critical fix for HEIC-to-JPEG conversions. Previously, when a client uploaded a HEIC image from an iPhone, the client-side conversion would keep the .heic extension even after turning it into a JPG. This caused nightmares for any server-side scripts or CDNs expecting standard mime types. WordPress 7.0 development has finally corrected this to use the .jpg extension properly.
Additionally, there is 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. This prevents a potential exploit where a contributor could bypass global CSS restrictions. Here is how I’ve been handling capability checks for custom block features recently:
<?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, currently an experiment, received significant polish this month. Specifically, semantic clarity was improved by aligning with WCAG patterns, and the top-level structure is now locked to prevent users from accidentally deleting the required wrapper blocks. Consequently, theme developers can now rely on a more stable DOM structure when writing CSS overrides.
Look, if this WordPress 7.0 development stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days and I know where the bottlenecks hide.
The Road Ahead for May 2026
WordPress 7.0 development is a reminder that architectural integrity wins over marketing deadlines. Pulling RTC was a painful but necessary surgery. For those of us building on this platform, the focus now shifts 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 are already behind schedule. Use the WordPress Playground to spin up a nightly build and start breaking things before May 20.
