WordPress Gutenberg 22.7 landed on March 11, 2026, and while it does not flip a switch and make your website suddenly “AI-powered,” it does something arguably more important: it lays the structural plumbing that every serious AI feature on WordPress will depend on for years to come. This is not a cosmetic update. It is infrastructure — the kind of groundwork that doesn’t make headlines on its own, but that makes everything downstream possible.
For site owners, content teams, WordPress developers, and digital marketers preparing for WordPress 7.0’s scheduled April 9, 2026 release, understanding what Gutenberg 22.7 actually ships — and what it does not — is essential. This post covers every meaningful change in the release, explains what each feature genuinely does in practice, and contextualizes the update within the broader WordPress AI roadmap heading into 2026.
What Is Gutenberg 22.7 and Why Does This Release Matter?
Gutenberg is the block editor that ships with WordPress, and it follows its own release cadence — publishing updates roughly every two weeks, ahead of major WordPress core releases. These biweekly drops allow the development team to iterate rapidly on editor features, experiment with new interfaces, and backport the best of those changes into the next major version of WordPress core.
Gutenberg 22.7 is notable not because it delivers finished AI features, but because it introduces the foundational components that WordPress 7.0 will rely on for AI integrations. Two of those components — the AI Connectors system and the Content Guidelines framework — are experimental, but they are also the most significant architectural additions to WordPress’s publishing stack in recent memory.
The release also ships several meaningful non-AI improvements: live previews for block style variation transforms, a more responsive Grid block visualizer, a WaveForm Player in the Playlist block, phpMyAdmin support in wp-env, and real-time collaboration now enabled by default. Each of these has practical relevance for editors and developers right now, independent of any AI roadmap.
The AI Connectors System: WordPress Gets a Centralized API Key Manager
Before Gutenberg 22.7, if you installed five different WordPress plugins that each wanted to call OpenAI’s API, you would configure five separate settings pages, paste your API key five times, and manage five different authentication flows. There was no standardized credential store. Every plugin built its own solution.
Gutenberg 22.7 changes that by introducing a new admin page under Settings > Connectors. This page acts as a centralized vault for AI service credentials. You enter your API key for a provider once, and every plugin on your site that uses the WordPress AI Client library can access those credentials through a unified internal routing system.
What the Connectors Page Actually Shows
When you navigate to Settings > Connectors in a WordPress installation running Gutenberg 22.7 (or WordPress 7.0 Beta), you see three sections: one for OpenAI, one for Anthropic (Claude), and one for Google (Gemini). Each section contains an API key input field and a save button. Once a key is saved, it is masked — you cannot view the full key again, which is standard practice for credential security.
The interface is, by the team’s own description, still in an experimental state. That label carries real meaning here: the underlying API (Settings > Connectors) and the PHP behavior for core backporting are actively being refined. The GitHub pull requests that shipped with this release (75833, 75948, 76014) show an active development cycle around dynamic provider registration, naming conventions with the _ai_ prefix, and integration with the broader WP AI Client registry.
What Connectors Are Not
It is worth being precise about what this feature does not do. The Connectors page is not itself an AI feature. It does not generate content. It does not write headlines, rewrite paragraphs, or suggest anything. It is credential management infrastructure. Connecting your OpenAI key in the Connectors panel does not immediately unlock any AI writing tools in the editor — those tools still depend on plugins that build on top of this infrastructure.
The distinction matters because some early coverage of this feature implied it unlocks AI writing capabilities in Gutenberg itself. That is not accurate. What it does is remove a significant friction point: instead of each AI plugin needing to build its own key-management interface, they can all rely on a single, standardized one.
The Developer-Facing API
For developers building AI-powered plugins on WordPress, the Connectors system pairs with the wp_ai_client_prompt
This approach mirrors what Jetpack has offered through WordPress.com for some time, but now extends the same pattern to self-hosted WordPress instances and the broader plugin ecosystem. Third-party provider support (Mistral, Cohere, etc.) is planned for WordPress 7.1. For the 7.0 cycle, only the three official provider plugins — OpenAI, Anthropic, and Google — can register on the Connectors page.
Content Guidelines: The Feature James LePage Calls the “Cornerstone” of WordPress AI
The second major AI-adjacent addition in Gutenberg 22.7 is Content Guidelines, described by James LePage — Automattic engineer and co-lead of the official WordPress AI team — as “a cornerstone feature to steer AI and how it interacts with your site.”
That framing deserves careful reading. LePage does not say Content Guidelines is an AI feature. He says it is the thing AI should depend on. The distinction reflects a specific design philosophy: before you give AI tools access to your WordPress site, the site should have a structured, machine-readable representation of what it expects from content. That is what Content Guidelines provides.
The Problem Content Guidelines Solves
Most organizations that operate a WordPress site have some form of content standards: a preferred voice and tone, structural rules for how posts should be organized, image guidance, accessibility requirements, how internal links should be used, and terminology preferences. These standards are almost never stored inside WordPress itself. They live in a Google Doc somewhere, a Confluence page, a onboarding PDF, or just the institutional knowledge of the person who has been editing the site for three years.
This creates two compounding problems. First, it means the standards are invisible at the moment of writing — the editor has to remember them, check them elsewhere, or simply not know they exist. Second, it means any tool operating on the site — a plugin, an automation script, or an AI assistant — has no way to access or apply those standards. The AI does not know your brand’s voice. It does not know that you never use the passive voice in headlines, or that you always link to a specific product page when mentioning a service category.
Content Guidelines gives those standards a canonical home inside WordPress itself.
What the Experimental Feature Includes
In Gutenberg 22.7, Content Guidelines ships as a set of experimental components:
- A new experimental REST API that allows external tools and plugins to retrieve site-wide content rules programmatically
- A custom post type for storing and managing content guidelines as structured data
- A UX layer covering four categories: site-wide guidelines, copy standards, image guidelines, and additional/custom guidelines
- Support for import and export so guidelines can move with a site, be reused across staging and production environments, or serve as templates for new sites
- Revision history so changes to guidelines are tracked over time
The design is notably not AI-specific. The guidelines are structured in plain language. A human editor can read them, follow them, and update them without any AI involvement. The premise is that a human-readable, machine-accessible store of standards creates compounding value regardless of whether AI is involved — and becomes dramatically more valuable once it is.
Four Specific Benefits Outlined by the WordPress AI Team
The official proposal from the WordPress AI team identifies four concrete outcomes that Content Guidelines enables:
1. A Single Source of Truth for Content Standards Rather than standards living in scattered documents, they live in WordPress itself. Any contributor — new or experienced — can access them during the act of writing.
2. Consistency Across Authors and Tools On multi-author sites, maintaining consistent voice, structure, and formatting is an ongoing operational challenge. When standards are part of the platform, every contributor and every tool works from the same reference.
3. More Steerable AI Behavior This is the AI-specific benefit. When an AI assistant can reference a site’s actual voice, terminology, structural preferences, and accessibility requirements, it produces site-specific output rather than generic content. The practical implication is fewer rounds of human editing to make AI-generated or AI-assisted content actually sound like the site it is being published on.
4. Guardrails for Agents As WordPress evolves to support autonomous agents — tools that act on a site’s behalf without human approval of each action — those agents need to understand what the site expects. Content Guidelines acts as a behavioral boundary that keeps agents aligned with brand and editorial standards.
What “Experimental” Means Here
Like the Connectors feature, Content Guidelines ships as an experiment. The underlying REST API and custom post type are not yet stable interfaces. The WordPress development team is actively gathering feedback on the schema, the fields, and which workflows matter most before committing to a long-term API design.
For site owners and marketers, this means Content Guidelines is available to explore in Gutenberg 22.7 and WordPress 7.0, but building production workflows around it today carries the same caveats as any early-stage feature: the API may change before it stabilizes.
Real-Time Collaboration Is Now On by Default
One of the most practically significant changes in Gutenberg 22.7 is not an AI feature at all. Real-Time Collaboration (RTC) — the ability for multiple users to edit the same post simultaneously, with changes appearing live for all active editors — is now enabled by default.
This matters because it changes the baseline behavior of every WordPress installation running Gutenberg 22.7 or later.
How RTC Works Under the Hood
WordPress’s real-time collaboration is built on Yjs, a Conflict-free Replicated Data Type (CRDT) framework. CRDTs are a class of data structures designed for distributed systems where multiple users may make changes simultaneously and those changes need to be merged without conflicts. The same general approach powers collaborative editing in modern productivity tools, though the specific implementation in WordPress uses polling-based synchronization as its transport layer — the same mechanism that powers the WordPress REST API — rather than persistent WebSocket connections.
This transport choice is intentional. Most shared hosting environments do not support persistent WebSocket connections. A polling-based architecture means RTC works on standard PHP hosting without requiring special server configuration, at the cost of some real-time latency compared to WebSocket-based implementations.
When two or more users open the same post, the editor signals that collaboration is active. When a user finishes editing a block and moves on, their changes sync to all connected editors. Updates to individual blocks appear with a brief visual highlight, indicating which area just changed. The session includes activity notifications — new in Gutenberg 22.7 via pull request 76065 — that inform collaborators when others join or leave the editing session.
The Default Behavior and Its Implications
Enabling RTC by default in Gutenberg 22.7 aligns the plugin’s behavior with what WordPress 7.0 will ship. The change does not override an admin’s intentional choice to disable the feature — if a site administrator has explicitly turned RTC off, that preference is preserved.
For teams with multiple editors, enabling RTC by default is a meaningful workflow change. The same post can now be edited simultaneously by different contributors without the document-locking mechanism that previously required one editor to check out a post before others could access it. For solo sites and single-author blogs, the change is invisible in practice — there is nothing to notice until a second user opens the same post.
Style Variation Transforms With Live Previews
Gutenberg 22.7 adds a live preview for style variation transforms — a practical quality-of-life improvement for anyone working with block styling in the editor.
Prior to this release, if you wanted to change a Heading block from one style variation to another (say, from a default style to a gradient style defined in the theme), you applied the transform and then evaluated the result. There was no way to preview how the change would look before committing to it.
With Gutenberg 22.7, the transform dropdown now displays a visual preview of each available style variation before you select it. The implementation matches the behavior already available for toolbar transforms, so both the inspector panel and the toolbar now behave consistently.
The update also extends style variations to patterns operating in contentOnly mode — an editing mode where users can change content inside a pattern without modifying its structure or layout. Style variations in contentOnly mode were previously unavailable, which limited the design flexibility of content-locked patterns.
For theme developers and design-heavy sites, these changes reduce the trial-and-error cycle when working with styled blocks. For editors on teams with defined brand patterns, the ability to preview variations before applying them reduces the risk of accidentally altering published content while experimenting.
Custom CSS Selectors in block.json: What Block Developers Gain
Block developers gain a meaningful new capability in Gutenberg 22.7: the ability to define custom CSS selectors inside block.json that Global Styles will honor.
Before this change, Global Styles applied CSS to a block’s root wrapper — the outermost element in the block’s rendered HTML. For simple blocks, this was adequate. For blocks with complex inner HTML structures — multiple nested elements, specific child elements that need independent styling — it created limitations. If you wanted Global Styles to target a specific <a> tag or a <span> inside a block, the system’s scoping to the root wrapper meant you had to use workarounds.
The new custom selector system allows block developers to declare, in block.json, which CSS selector the Global Styles “Custom CSS” feature should target. This enables direct styling of inner elements through the same interface users already use for block-level custom CSS — no workarounds, no additional specificity battles.
For theme authors and plugin developers, this closes a meaningful gap in the Global Styles API. It allows more expressive block customization through the standard editor interface rather than requiring site-specific CSS overrides in child themes.
Grid Block and Playlist Block: Practical Editing Improvements
Two additional feature-level updates in Gutenberg 22.7 improve specific editing workflows without requiring any configuration.
Grid Block Visualizer
The Grid block’s Visualizer — the overlay that helps editors understand and adjust grid column configurations — is now synchronized more quickly and accurately with the selected number of columns. Before this fix, there was a noticeable lag and occasional misalignment between the column count input and what the Visualizer showed in the editor canvas.
The improvement (pull request 75820) makes grid layout editing more reliable and immediate. When you change the column count, the Visualizer updates instantly, so what you see in the editor accurately reflects the configured grid. For layout-heavy sites built on the grid block, this is the kind of fix that removes a persistent friction point from daily editing work.
Playlist Block WaveForm Player
The Playlist block — still in experimental status — now includes a WaveForm Player visualizer. When a user plays an audio file from a Playlist block on the frontend, the waveform provides a visual representation of the audio, which also opens design possibilities for how the Playlist block displays in different theme contexts.
The WaveForm Player does not change the block’s audio playback behavior. It adds a visual element. For sites that publish audio content — podcasts, music, voice recordings, interviews — this adds a frontend presentation layer that matches what users expect from modern audio players.
Additional Technical Improvements: phpMyAdmin, Components, and Bug Fixes
Beyond the headline features, Gutenberg 22.7 ships a set of technical improvements that matter to developers and site maintainers:
phpMyAdmin in wp-env: WordPress’s local development environment tool (wp-env) now includes optional phpMyAdmin support. A new boolean configuration option (phpmyadmin: true/false) allows developers to enable a database management interface directly within their local environment. For developers who regularly work with database queries or data inspection during plugin and theme development, this removes the need to set up a separate database client.
Button text overflow fix: A word-break: break-word rule has been added to button components, fixing a display issue where buttons with unusually long text strings would overflow their container boundaries rather than wrapping.
Media Library optimization: Image loading for media thumbnail fields has been optimized for performance, reducing overhead in the Media Library UI for sites with large media collections.
Color Picker refinement: The ColorPicker component has been refactored to preserve hue and saturation values when users drag colors to achromatic values (whites, blacks, grays). Previously, the hue/saturation context was lost in those edge cases, making it harder to return to a chromatic value from an achromatic one.
RTC stability fixes: Fourteen separate bug fixes related to Real-Time Collaboration shipped in Gutenberg 22.7, addressing issues with CRDT document persistence on save, emoji and surrogate pair synchronization, disconnect dialog behavior, and stale awareness state on browser refresh. The volume of RTC bug fixes reflects active stabilization work ahead of WordPress 7.0’s April 9 release.
How Gutenberg 22.7 Connects to WordPress 7.0
WordPress 7.0 is scheduled for release on April 9, 2026. It is the first major WordPress release of the year and represents the culmination of “Phase 3” of the Gutenberg project — the phase focused on collaboration, workflow, and what Automattic has labeled “AI-readiness.”
Gutenberg 22.7 is, in practical terms, a staging update for 7.0. The features being tested here — Connectors, Content Guidelines, Real-Time Collaboration enabled by default — will either ship in core with 7.0 or will be available as experimental extensions accessible from the WordPress plugin directory.
The Abilities API: The Other Half of WordPress’s AI Infrastructure
Gutenberg 22.7’s AI infrastructure work pairs with another development that is happening in parallel: the WordPress Abilities API. While Connectors and Content Guidelines focus on managing credentials and defining editorial standards, the Abilities API addresses a different question: how does an AI agent understand what a WordPress site can do?
The Abilities API creates a central registry of site capabilities — a machine-readable description of what actions are available, under what conditions, and with what permissions. When combined with the Model Context Protocol (MCP), this allows AI assistants like Claude, ChatGPT, and Gemini to discover a site’s capabilities, request permission to take specific actions, and execute those actions within defined boundaries.
The three-layer stack that is emerging looks like this:
- Connectors handle authentication: which AI services can talk to this site, and using which credentials
- Content Guidelines handle context: what standards should AI apply when working with this site’s content
- Abilities API handles capability discovery: what can be done on this site, and under what conditions
None of these layers is interesting in isolation. Together, they represent a coherent architecture for integrating AI into WordPress publishing workflows — one where the site owner defines the terms and the AI operates within them.
What This Means for Site Owners, Content Teams, and Developers
The practical takeaways from Gutenberg 22.7 differ depending on your role.
For Site Owners and Non-Technical Users
The most immediately relevant change is Real-Time Collaboration being enabled by default. If your team has multiple editors, Gutenberg 22.7 removes the post-locking friction that has existed since WordPress’s earliest days. You do not need to configure anything. The change is automatic, and it aligns WordPress’s collaborative behavior with tools your team may already be familiar with.
The AI Connectors and Content Guidelines features exist for you to explore, but they are not ready for production reliance. Think of them as features you should understand today so you can plan for them in Q3 and Q4 of 2026, when they are likely to be more stable.
For Content Teams and Editors
The style variation preview change is genuinely useful immediately. If your site uses block styles defined by your theme or design team, you can now preview those variations before applying them — which reduces unintended formatting changes and speeds up the styling process.
For teams that already have an editorial style guide, the Content Guidelines feature is worth investigating as an experiment even in its current state. Getting familiar with the interface now, understanding what fields it supports, and testing how it behaves in your workflow will position your team well for when the feature stabilizes.
For WordPress Developers and Agencies
The Custom CSS selector support in block.json is a concrete improvement to the block development workflow. If you build or maintain custom blocks, reviewing the new customSelector property in the Global Styles documentation and updating relevant blocks to take advantage of it is a worthwhile short-term task.
The Connectors API, while experimental, warrants attention for any agency building AI-enabled plugins or client sites. Understanding how provider registration works, which providers are supported in the current cycle, and what the extension hooks look like will give you a head start on building plugins that behave as first-class citizens in the WordPress 7.0 AI ecosystem.
The Broader Context: WordPress as a Publishing Platform in 2026
WordPress powers approximately 43% of websites on the internet. That number represents an enormous range of publishing contexts: individual bloggers, regional news organizations, enterprise content teams, e-commerce operations, and everything between. The challenge the WordPress AI team faces is designing an AI integration approach that serves all of those contexts without locking any of them into a single model vendor or a single capability set.
The architectural choices in Gutenberg 22.7 reflect that constraint deliberately. By making the Connectors system provider-agnostic, WordPress avoids the situation where choosing WordPress means choosing OpenAI (or any other single provider). By making Content Guidelines independent of AI entirely, the team ensures the feature has standalone value even for teams that have no interest in AI publishing tools. By building on top of the WP AI Client registry and MCP, the Abilities API creates interoperability with the broader ecosystem of AI assistants rather than building a proprietary interface.
The result is a publishing platform that is designed to accommodate AI without requiring it, and to integrate with whatever AI tools become standard over the next two to five years — rather than betting on any single tool being the right one.
This is a meaningfully different approach from platforms that have integrated AI by adding an “AI Write” button that calls a single model. Those integrations are faster to ship and easier to market, but they create vendor dependency and offer limited site-specific customization. WordPress’s approach takes longer to build but creates a more durable and flexible foundation.
What to Actually Do With Gutenberg 22.7 Right Now
Given the mix of stable and experimental features in this release, here is a practical guide to action:
Install the update. Gutenberg 22.7 is available from the WordPress plugin directory. If your site uses the default WordPress core editor without the Gutenberg plugin, these changes will arrive with WordPress 7.0 in April.
Test Real-Time Collaboration with your team. Open a draft post, share the URL with a colleague, and have them open the same post. Observe how the collaboration signals appear, how edit synchronization works, and whether the session activity notifications help or create noise. Testing this now, before 7.0 ships, gives you time to prepare your team and identify any workflow adjustments needed.
Explore the Connectors page. Navigate to Settings > Connectors (if using the Gutenberg plugin with an experimental flag enabled) and review the interface. You do not need to enter a live API key to understand how the system works. Understanding the interface today means less time spent on orientation when it ships as a stable feature.
Draft a Content Guidelines document. Even before the feature is production-ready, the act of articulating your site’s content standards in a structured format — voice and tone, structural preferences, image guidance, accessibility requirements — is useful. You will be ready to import those standards when the REST API stabilizes, and the process often surfaces editorial inconsistencies that are worth fixing regardless of any technology.
Update your block.json files. For developers maintaining custom blocks, review whether any of your blocks would benefit from the new custom CSS selector support in Global Styles, and update block.json accordingly.
Frequently Asked Questions About WordPress Gutenberg 22.7
What exactly is Gutenberg 22.7?
Gutenberg 22.7 is a biweekly update to the Gutenberg block editor plugin, released on March 11, 2026. It ships several improvements to the WordPress editing experience alongside two experimental AI-infrastructure features — the Connectors system and Content Guidelines — that are designed to prepare the editor for AI integrations coming in WordPress 7.0 and beyond.
Does Gutenberg 22.7 add AI writing tools to WordPress?
No. Gutenberg 22.7 does not add AI writing, content generation, or AI editing tools to the WordPress editor. What it adds is the infrastructure that AI tools will depend on: a centralized credential manager (Connectors) for API keys, and a structured store for content standards (Content Guidelines). Actual AI writing features require separate plugins built on top of this infrastructure.
What is the AI Connectors feature in Gutenberg 22.7?
The Connectors feature adds a new admin page at Settings > Connectors where site owners can store API keys for AI service providers. Currently supported providers are OpenAI, Anthropic (Claude), and Google (Gemini). Once a key is stored, any plugin using the WordPress AI Client library can access it through a unified internal API, removing the need for individual plugins to manage their own credential storage.
Is the Connectors page stable and ready for production use?
No. The Connectors page and its underlying API are explicitly marked as experimental in Gutenberg 22.7. The interfaces may change before they stabilize with WordPress 7.0 or later releases. It is safe to explore the feature, but building production workflows dependent on its current API structure is not recommended at this stage.
What is the Content Guidelines feature and how does it work?
Content Guidelines is an experimental feature that creates a structured, machine-readable store for site-wide editorial standards — things like voice and tone, structural rules for posts, image guidance, and accessibility requirements. It ships as a new custom post type with a REST API, along with a UI for creating, editing, importing, and exporting guidelines. The feature is designed to give AI tools, plugins, and human editors a single source of truth for how content should be written and managed on a specific site.
Does Content Guidelines require AI to function?
No. Content Guidelines is explicitly designed to be independent of AI. The feature has value as a centralized editorial reference system regardless of whether any AI tools are in use. However, the design intends for AI tools on the site to reference these guidelines, which is why the feature is described as something AI should depend on rather than depend on AI.
What is Real-Time Collaboration in Gutenberg 22.7, and is it safe to use?
Real-Time Collaboration allows multiple users to edit the same WordPress post simultaneously, with changes syncing across all active editors without requiring a page reload. In Gutenberg 22.7, RTC is enabled by default. It is built on Yjs, a CRDT framework, and uses polling-based synchronization compatible with standard PHP hosting. The feature is considered stable enough to ship with WordPress 7.0, though Gutenberg 22.7 includes fourteen bug fixes related to RTC edge cases — indicating active stabilization work is ongoing.
Will Real-Time Collaboration override my site’s existing collaboration settings?
No. The Gutenberg 22.7 release notes specify that the default-on behavior for RTC does not override an administrator’s intentional choice to disable the feature. If your site has explicitly disabled RTC, that preference is preserved.
What is WordPress 7.0 and when will it be released?
WordPress 7.0 is the next major release of WordPress core, scheduled for April 9, 2026. It represents the culmination of “Phase 3” of the Gutenberg project, which has focused on collaboration features, workflow improvements, and laying the groundwork for AI integrations. Key features expected in 7.0 include native Real-Time Collaboration, the AI Client and Connectors system, the new DataViews admin interface, the Abilities API, and various block editor enhancements that have shipped in recent Gutenberg releases.
What is the WordPress Abilities API, and how does it relate to Gutenberg 22.7?
The Abilities API is a separate initiative — developed alongside but not shipped in Gutenberg 22.7 — that creates a machine-readable registry of what a WordPress site can do. It works with the Model Context Protocol (MCP) to allow AI assistants like ChatGPT, Claude, and Gemini to discover site capabilities, request permissions, and execute tasks within defined boundaries. Gutenberg 22.7’s Connectors and Content Guidelines features are part of the same ecosystem: Connectors handle authentication, Content Guidelines handle editorial context, and the Abilities API handles capability discovery.
What AI providers does WordPress currently support through Connectors?
As of Gutenberg 22.7 and the WordPress 7.0 Beta cycle, three AI providers are officially supported: OpenAI, Anthropic (Claude), and Google (Gemini). Support for additional third-party providers — such as Mistral or Cohere — is scheduled for WordPress 7.1. Currently, only the three official provider plugins can register on the Connectors page.
Does Gutenberg 22.7 change how CSS works for custom blocks?
Yes. Block developers can now define custom CSS selectors in block.json that Global Styles will honor. Previously, Global Styles was limited to applying styles to a block’s root wrapper element. The new custom selector support allows Global Styles to target specific inner elements within a block — a <span>, an <a> tag, or any other inner element a developer specifies — through the standard Custom CSS interface.
What changed in the Grid block?
The Grid block Visualizer — the overlay that shows the current grid column configuration — is now synchronized more quickly and accurately with the selected column count. Before Gutenberg 22.7, there was a lag between adjusting the column count and seeing the Visualizer update to reflect it. The fix makes the Grid block’s visual feedback immediate and accurate during layout editing.
What is the WaveForm Player in the Playlist block?
The Playlist block — still experimental — now includes a WaveForm Player that displays a visual waveform representation of audio files as they play. This adds a visual dimension to the Playlist block’s frontend display and opens design possibilities for how audio content is presented. The Playlist block’s core playback functionality is unchanged.
What does phpMyAdmin support in wp-env mean for developers?
wp-env is WordPress’s official local development environment tool. Gutenberg 22.7 adds optional phpMyAdmin integration, enabled via a new phpmyadmin boolean configuration option in the .wp-env.json file. When enabled, phpMyAdmin is available within the local environment for database inspection and management. This is useful for developers who need direct database access during plugin or theme development without setting up a separate database client.
Should I update to Gutenberg 22.7 now, or wait for WordPress 7.0?
For most sites, updating to the Gutenberg plugin is a low-risk way to preview features before they ship in core. Gutenberg 22.7 includes bug fixes for Real-Time Collaboration, stability improvements to the editor components, and the experimental AI infrastructure features that will ship with 7.0. If your site relies heavily on custom blocks or third-party plugins that integrate deeply with the editor, reviewing the changelog for any potential conflicts before updating is advisable — a standard best practice for any Gutenberg update.
How does Content Guidelines handle multiple languages or multilingual sites?
The Gutenberg 22.7 release does not specify multilingual support for Content Guidelines in its current experimental state. The feature is designed to manage site-wide editorial standards, and multilingual scenarios — where different language versions of a site may have different voice, tone, or structural requirements — are among the use cases the development team is collecting feedback on before finalizing the API design. If you operate a multilingual WordPress site, the tracking issue (#75171 on GitHub) is the appropriate place to contribute your requirements.
Will WordPress ever integrate AI directly into the block editor without plugins?
The WordPress development philosophy has historically favored extensibility over built-in features for everything beyond core editing functionality. The current direction suggests that AI writing features are likely to remain plugin territory, while the core editor provides the infrastructure — Connectors, Content Guidelines, Abilities API — that those plugins depend on. This approach keeps the core editor lightweight and avoids creating a situation where switching AI providers requires changing CMS infrastructure.
How does Gutenberg 22.7 affect SEO and content quality?
Gutenberg 22.7 does not change search engine behavior directly. However, two features have indirect SEO relevance: the Content Guidelines system, when mature, enables more consistent on-brand content creation, which contributes to topical authority and editorial coherence over time; and Real-Time Collaboration, by reducing friction in multi-author workflows, can accelerate publishing cycles and reduce the time between content creation and publication. Neither of these is a ranking factor by itself, but both contribute to the operational quality and consistency of a content program.
Gutenberg 22.7 is, at its core, a version about infrastructure. The features that will likely be most discussed in coverage of WordPress 7.0 — AI writing tools, autonomous agents, seamless model integration — are not present yet. What is present are the three foundational layers that make those features architecturally sound when they arrive: a credential vault that any plugin can use, an editorial standard store that any tool can reference, and a capability registry that any AI agent can query. For teams building on WordPress, understanding these foundations now is the right preparation for a platform that is set to change significantly in the months ahead.
Frequently Asked Technical Questions
How do I access the Connectors settings page in Gutenberg 22.7?
The Connectors page appears under Settings > Connectors in the WordPress admin sidebar when you have the Gutenberg plugin (version 22.7 or later) installed and active. Note that the feature is experimental and may require an experimental flag to be enabled, depending on your WordPress configuration.
Can I use both the Gutenberg plugin and WordPress core simultaneously?
Yes. The Gutenberg plugin is designed to run alongside WordPress core and extends the core editor. Running the plugin gives you access to features — including those in 22.7 — ahead of their inclusion in a major core release. When WordPress 7.0 ships in April, the features that graduate to core will be available without the plugin.
Are the Content Guidelines importable from an external file?
Yes. Gutenberg 22.7 includes import and export functionality for Content Guidelines (pull request 76155). Guidelines can be exported from one site and imported to another, making it possible to reuse a consistent standard across multiple WordPress installations or to migrate guidelines between staging and production environments.
What is the _ai_ prefix added to connector settings names?
Pull request 75948 adds the _ai_ prefix to all connector-related settings names in the WordPress options table. This is a namespacing convention that avoids conflicts with other plugins storing data in the same table and makes AI-related settings identifiable in the database. The naming convention is part of the code quality improvements included in the release.
How does RTC handle conflicts when two users edit the same block simultaneously?
WordPress’s Real-Time Collaboration uses Yjs, a Conflict-free Replicated Data Type framework. CRDT implementations are designed to merge concurrent edits deterministically — meaning two edits to the same block can be merged into a consistent result without requiring either user to manually resolve a conflict. The specific merge behavior in WordPress’s block editor context continues to be refined, as reflected in the fourteen RTC-related bug fixes in Gutenberg 22.7.
The trajectory of WordPress through the rest of 2026 is clearer after Gutenberg 22.7 than it was before it. The AI infrastructure is being built methodically, with a deliberate separation between the credential layer, the context layer, and the capability layer. For anyone managing a content-driven website on WordPress — whether it is a single-author blog, a publication with dozens of contributors, or an enterprise digital presence — the decisions being made in these Gutenberg releases will shape how editorial workflows function for the next several years. Staying informed about them is not optional for teams that want to be prepared rather than reactive.
About ALM Corp
ALM Corp is a full-service digital marketing agency that has been helping businesses grow their digital presence since 2006. With more than $7 billion in sales generated, 5,700+ websites launched, and over one million leads delivered for clients, ALM Corp brings deep expertise to every dimension of digital marketing — from SEO and paid media to web design, content strategy, data analytics, and technology solutions.
As WordPress continues its evolution toward AI-assisted publishing workflows, ALM Corp’s services are directly relevant to businesses navigating that transition. Whether that means optimizing your WordPress site architecture for the Content Guidelines and Connectors systems coming in 7.0, building an editorial content strategy that performs well in both Google search and AI-generated overviews, or managing a structured SEO program that anticipates how AI-assisted content publishing changes competitive dynamics — ALM Corp operates at the intersection of technology and business performance.
For organizations looking to get ahead of the WordPress 7.0 changes, or to build a content and SEO program that converts traffic into measurable revenue, ALM Corp’s digital strategy team is available to assess your current position and identify the highest-value next steps. ALM Corp works with businesses across North America and globally as both a direct agency partner and a white-label service provider for agencies looking to expand their WordPress and content marketing capabilities.
