Release snapshot
– Version: WordPress 7.0
– Release date: May 20, 2026
WordPress 7.0 shifts the project toward collaborative workflows and AI integration rather than purely single-author publishing. The release introduces real-time collaboration, a core AI scaffolding layer, and a redesigned, visual revisions experience. Below is a concise breakdown of what changed and who benefits.
1) Real-time collaboration (RTC)
What it is: Google Docs–style simultaneous editing for posts and pages so collaborators can see each other’s changes live.
Key details:
– Uses CRDTs (Conflict-free Replicated Data Types) to resolve concurrent edits.
– Uses HTTP polling by default to remain compatible with a wide range of hosts.
– Initially limited to two simultaneous collaborators to reduce hosting strain.
– Hosts can supply alternate transport/storage implementations; developers can tune polling via JS filters.
– RTC is disabled when traditional metaboxes are present, encouraging plugin authors to adopt newer approaches.
Should you care? RTC is aimed at teams, newsrooms, and enterprise workflows more than solo bloggers. It’s currently opt-in and still early; useful when live collaboration matters, but many writers will keep drafting alone. Expect further iterations as adoption and hosting feedback come in.
2) AI foundation (Connectors API + wp_ai_client_prompt)
What it is: a framework rather than a set of built-in AI features. WordPress 7.0 provides centralized credential management and a provider-agnostic client to make adding AI capabilities easier for plugins and themes.
Key details:
– New Connectors screen in wp-admin to store and manage API keys for services such as OpenAI, Claude, Gemini, and others.
– Connectors API lets plugins manage external service credentials in a standardized way (not limited to AI providers).
– wp_ai_client_prompt(): a PHP helper that sends prompts to large language models without tying plugins to a specific vendor.
Should you care? Yes, especially if you build or maintain plugins. This architecture centralizes credentials and lets WordPress act as a neutral orchestration layer for AI services, simplifying integration and improving security practices for third-party developers.
3) Visual revisions
What changed: Revisions are now integrated into the main editor with a visual, color-coded interface rather than a separate screen.
Key features:
– Timeline slider in the editor header for browsing versions.
– Color coding: yellow = modified, red = deleted, green = added.
– Minimap on the scrollbar to show where changes occurred in the document.
– While viewing history, the primary action becomes “Restore” instead of “Publish.”
Should you care? The new UI is friendlier for non-technical users and makes spotting edits easier. However, it removes some longtime power-user features: raw HTML source isn’t available in the revisions view, and you can only compare a selected revision with its immediate predecessor (not arbitrary pairs). It’s a trade-off between accessibility and granular control.
Developer highlights
– PHP-only block registration: Register blocks using only PHP (no JS build step). register_block_type with autoRegister and a render_callback provides automatic sidebar controls for compatible attributes — ideal for simple, server-rendered blocks.
– Pattern overrides for custom blocks: Pattern Overrides now work for any block that supports Block Bindings, enabling synced layouts with variable instance content.
– Client-side Abilities API: A JavaScript counterpart to the server Abilities API (packages: @wordpress/abilities and @wordpress/core-abilities) that supports browser-agent and extension integrations — a foundation for richer agent/AI interactions.
– Custom CSS per block instance: Add per-instance CSS in a block’s sidebar (write declarations only; use & for nesting) to style individual blocks without creating custom classes.
Design and editing improvements
– Navigation overlays: More control over mobile hamburger menus, 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 content-only mode with editable fields in a simplified sidebar, which reduces accidental layout breaks while still allowing full detachment for power users.
– Viewport-based block visibility: Toggle block visibility for desktop, tablet, and mobile directly from the toolbar — functionality that previously required plugins.
Command Palette
A global Command Palette remains available via ⌘K / Ctrl+K, letting you quickly find settings and actions anywhere in the admin.
Verdict
WordPress 7.0 is a solid, direction-setting release. Real-time collaboration and visual revisions will spark debate about who benefits most, but the larger signal is clear: WordPress intends to be a neutral orchestration layer for AI services and a platform that supports more collaborative content workflows. The Connectors API and wp_ai_client_prompt are particularly promising foundations for future features and third‑party innovation. Kudos to contributors — there’s lots here for developers and teams to build on.
Your turn
What do you think of WordPress 7.0? Is there a feature you’re excited to try or one you think needs work?
Performance tip
A few targeted fixes (caching, optimized assets, image compression, and hosting tweaks) often cut page load times substantially. There are many guides and weekly newsletters that walk through practical optimizations if you want step-by-step help.