Gutenberg 22.7 is out. Most releases in the two-week cycle are incremental polish, but this one is laying groundwork for WordPress 7.0: the first official “Connectors” API, and a serious push on Real-Time Collaboration (RTC).
I have spent 14 years watching WordPress grow from a blogging tool into an application framework. Some of these experimental features move faster than I would like, but the Gutenberg 22.7 features are aimed at bottlenecks that agencies actually hit.
The new Connectors API
The headline is a Connectors page under Settings, and behind it an API that unifies how WordPress talks to outside services such as OpenAI. Until now every plugin developer built their own API key screen, and the admin filled up with a dozen versions of the same form. Core finally gives you one standard place to manage those connections.
It ships with an OpenAI demonstration, but the useful part is the extension hooks, which let you register your own providers. That is a pragmatic call: “Agentic Commerce” with a dozen competing authentication methods would be miserable to support. If you followed Gutenberg 22.6 Features, you will recognize how this sits on top of the new revisions logic.
Real-time collaboration is on by default
RTC is no longer a hidden experiment. It is enabled by default, so two people can work on the same post without running into the “This post is currently being edited” lock. The syncing runs on CRDTs (Conflict-free Replicated Data Types).
One warning from experience: legacy meta boxes. Custom fields that are not RTC-aware can produce race conditions, so if your site leans on non-Gutenberg meta, put this through staging before it reaches production. The official Gutenberg documentation has more on handling the transition.
Style variation transforms and previews
Style variation transforms now render a live preview in the editor, and the variations are available for patterns in contentOnly mode. Choosing one stops being a guessing game. It builds on the CSS work from the Gutenberg 22.5 release.
Working with the Content Guidelines API
Another experimental addition is Content Guidelines, where site owners define editorial rules through a custom post type and a new REST API. Here is roughly how you would fetch those guidelines for 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' );
wp-env picks up phpMyAdmin
If you develop locally with wp-env, Gutenberg 22.7 adds built-in phpMyAdmin support, switched on in your .wp-env.json file. It saves a trip to an external tool when you just need to look at a transient or a stuck background job.
If these Gutenberg 22.7 features are eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
Where WordPress 7.0 is heading
The shift under way is from page builder to collaboration platform. Connectors plus a maturing RTC point at an editor where AI agents and several people work on the same post at once. The features still marked experimental are the part of the Gutenberg 22.7 update worth reading closely. Open pull requests live in the Gutenberg GitHub Repository.
