Gutenberg 22.7 has just been released, and if you haven’t been paying attention to the bi-weekly cycle, now is the time to start. While many of these updates feel like incremental polish, this specific version is clearly laying the architectural groundwork for WordPress 7.0. Specifically, we are seeing the first official “Connectors” API and a massive push for Real-Time Collaboration (RTC).
I’ve spent the last 14 years watching WordPress evolve from a simple blogging tool into a complex application framework. Sometimes these “experimental” features feel like they’re moving too fast, but the Gutenberg 22.7 features we’re seeing today are solving real bottlenecks for agency workflows. Let’s break down what actually matters for developers and site owners.
The New Connectors API: AI Infrastructure
The headline feature is the new “Connectors” admin page under Settings. This isn’t just another settings screen; it’s an API intended to unify how WordPress talks to external services like OpenAI. For years, every plugin developer had to build their own “API Key” settings page, leading to a fragmented UI. Now, WordPress is providing a standardized way to manage these connections.
Currently, it includes an OpenAI demonstration, but the real power lies in the extension hooks. You can now register your own providers. This is a pragmatic move to ensure that as we move toward “Agentic Commerce,” we aren’t wrestling with a dozen different authentication methods. If you’re following the progress from Gutenberg 22.6 Features, you’ll see how this builds on the new revisions logic.
Real-Time Collaboration is Now Enabled by Default
This is the “Google Docs” moment for WordPress. Real-Time Collaboration (RTC) is no longer a hidden experiment; it’s on by default. Consequently, multiple users can edit the same post without the dreaded “This post is currently being edited” lock. This relies on CRDTs (Conflict-free Replicated Data Types) to sync changes instantly.
Senior Dev Tip: While this is great for productivity, be careful with legacy meta boxes. I’ve seen custom fields that aren’t RTC-aware cause race conditions. If your site relies heavily on non-Gutenberg custom meta, you might want to test this in a staging environment before shipping. You can find more about handling these transitions in the official Gutenberg documentation.
Style Variation Transforms & Previews
UI friction is the enemy of adoption. In 22.7, style variation transforms now display a live preview in the editor. Furthermore, these variations are available for patterns in contentOnly mode. This makes the editor feel significantly more professional and less like a guessing game. It builds on the CSS improvements we saw in the Gutenberg 22.5 release.
Interacting with the Content Guidelines API
Another experimental addition is the “Content Guidelines” system. This allows site owners to define editorial rules via a custom post type and a new REST API. Here is a conceptual example of how you might fetch these guidelines via the REST API to use in a custom validation script:
<?php
/**
* Conceptual example: Fetching Content Guidelines
* To ensure your content follows site-wide standards.
*/
function bbioon_fetch_site_guidelines() {
$response = wp_remote_get( get_rest_url( null, '/wp/v2/content-guidelines' ) );
if ( is_wp_error( $response ) ) {
return [];
}
$guidelines = json_decode( wp_remote_retrieve_body( $response ), true );
// Logic to enforce these rules during post save or via a custom block
return $guidelines;
}
add_action( 'init', 'bbioon_fetch_site_guidelines' );
Developer Experience: wp-env & phpMyAdmin
For those using wp-env for local development, Gutenberg 22.7 introduces built-in phpMyAdmin support. Specifically, you can now enable it in your .wp-env.json file. This is a massive quality-of-life update for those of us who need to quickly debug a transient or a stuck background job without reaching for external tools.
Look, if this Gutenberg 22.7 features stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Future of WordPress 7.0
We are seeing the transition from a “page builder” to a “collaboration platform.” The addition of the Connectors API and the maturation of RTC suggests that WordPress is preparing for a world where AI agents and multiple humans work together in the same editor. While some features are labeled “experimental,” they are the most important part of the Gutenberg 22.7 update to understand if you want to stay ahead of the curve. For more technical deep dives, check the Gutenberg GitHub Repository.
