WordPress 7.0 is positioned as a major redefinition of the platform rather than a routine editor update. The release (May 20, 2026) focuses on real-time collaboration, a provider-agnostic AI foundation, and a more visual approach to revisions—features that signal a strategic shift toward team workflows and third-party AI integrations.
Real-time collaboration (RTC)
The marquee capability lets multiple people edit the same post or page in real time, similar to Google Docs. Key implementation details:
– Uses CRDTs (Conflict-free Replicated Data Types) to resolve concurrent edits.
– Runs over HTTP polling to maximize compatibility with diverse hosting setups.
– Initially limited to two simultaneous collaborators to reduce load on shared hosts.
– Hosts and developers can swap the transport or storage; JS filters let plugins alter polling behavior.
– RTC is disabled when classic metaboxes are present, encouraging plugin authors to modernize.
Who benefits: RTC seems aimed at newsrooms, editorial teams, and enterprises. Solo authors and small blogs will likely stick with single-author drafts for now. The feature was planned to be enabled by default but is opt-in after feedback—an early iteration worth watching.
AI foundation (Connectors API + wp_ai_client_prompt)
Rather than bundling AI features, WordPress 7.0 provides the plumbing for others to build on:
– A Connectors screen in wp-admin to manage API keys for OpenAI, Anthropic, Gemini, and other services.
– A Connectors API plugins can use to store and expose external-service credentials (not limited to AI).
– A provider-agnostic PHP helper, wp_ai_client_prompt(), lets devs send prompts to LLMs without wiring provider-specific logic.
Why this matters: WordPress is positioning itself as a neutral orchestration layer for AI, making integrations easier and more secure. That should speed third-party innovation without WordPress shipping a branded model of its own.
Visual revisions
Revisions are now visual and integrated directly into the editor rather than hidden in a list.
Highlights:
– Timeline slider in the editor header to move through versions.
– Color-coded changes: yellow for modified, red for deleted, green for added.
– A minimap on the scrollbar showing where edits occurred.
– A Restore button appears when viewing history, replacing Publish for that context.
Limitations: You see rendered content rather than raw HTML, and comparisons are limited to a selected revision versus its immediate predecessor—not arbitrary pairwise diffs. The UI will be more approachable for non-developers, though power users may miss the classic HTML diff.
Developer-focused changes
– PHP-only block registration: Simple server-rendered blocks can be registered with PHP alone (autoRegister + render_callback), removing the JS build step for many cases.
– Pattern overrides for custom blocks: Synced patterns can now allow instance-specific content for any block that supports Block Bindings, not just core text/image/button types.
– Client-side Abilities API: JavaScript equivalents to server abilities (@wordpress/abilities, @wordpress/core-abilities) hint at richer agent and extension interactions.
– Custom CSS per block instance: A CSS input in the block sidebar accepts declarations (use & for nesting) so authors can add scoped styles without writing selectors.
Design and content-editing improvements
– Navigation overlays: More control over mobile menus with overlay template parts, built-in patterns, an always-visible submenu toggle, and the ability to create pages from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only mode with simplified sidebar fields; you can detach a pattern when you need full layout control—useful for client handoffs.
– Viewport-based block visibility: Toggle visibility per device (desktop, tablet, mobile) from the toolbar—functionality that used to require plugins.
Command Palette everywhere
The Command Palette is now globally available—press ⌘K or Ctrl+K to jump to settings, blocks, and actions from anywhere in the editor.
Verdict
Overall, WordPress 7.0 is a meaningful release. Some features (RTC especially) will feel niche to many users today, but the platform’s broader direction is clear: enable team workflows and act as a neutral layer for AI integrations. The Connectors API and wp_ai_client_prompt() are particularly promising for developers, because they make secure, provider-agnostic AI tooling practical inside WordPress.
What to try first: If you work on a team, test RTC in a controlled environment. If you build plugins or themes, explore the Connectors API and PHP-only block registration. If you hand off sites to clients, the content-focused patterns and visual revisions are worth evaluating.
What do you think of WordPress 7.0? Any feature you’re especially excited to use or skeptical about?
Want to speed up your WordPress site? A short course can help you cut load times dramatically. Enter your email on the linked signup to receive the course and a weekly newsletter (unsubscribe anytime).