Release date: May 20, 2026
Overview
WordPress 7.0 is one of the more ambitious updates in years — not just incremental improvements but a visible reframing of core priorities. The release pushes WordPress toward live collaboration, a neutral AI integration layer, and more visual, user-friendly editing tools. Many changes are aimed at teams, developers, and site builders, though some features will also benefit regular users.
1) Real-time collaboration (RTC)
The headline feature is live, multi-person editing inside the post/page editor, similar to Google Docs.
What to know:
– Conflict resolution uses CRDTs (Conflict-free Replicated Data Types).
– Transport relies on HTTP polling to maximize compatibility across hosts.
– To limit server load, the initial rollout allows only two simultaneous collaborators.
– Hosts can swap transport/storage implementations; developers can tune polling through JS filters.
– RTC is disabled if classic metaboxes are present, encouraging plugins to modernize integrations.
– After feedback, RTC is opt-in rather than enabled by default.
Who should care? Mostly teams, newsrooms, and enterprise setups that need synchronous editing. Solo writers who prefer private drafts may not use it immediately, but this is a foundational step that could expand into a broadly useful feature.
2) AI plumbing: Connectors API and wp_ai_client_prompt()
Instead of baking specific AI tools into core, 7.0 provides the infrastructure so plugins and services can connect to models and APIs.
What’s included:
– A new Connectors screen in wp-admin for managing API keys and credentials for providers like OpenAI, Anthropic (Claude), Google (Gemini), and others.
– A Connectors API developers can use to store and manage external service credentials; it isn’t limited to AI services.
– A provider-agnostic helper, wp_ai_client_prompt(), for sending prompts to LLMs from PHP.
Why this matters:
This is a neutral, extensible approach: core handles credential management and a common client interface, while third parties build the features and UI. Developers win first — they can add AI capabilities without reinventing credential storage or prompting logic.
3) Visual revisions
The old separate revisions screen is replaced by an inline, visual history experience inside the editor.
Key elements:
– Timeline slider in the editor header to scrub through versions.
– Color-coded diffs: yellow for modified, red for deleted, green for added content.
– A minimap on the scrollbar indicating where changes occurred.
– A Restore button when viewing past versions.
Caveats:
The new UI is more approachable for non-technical users, but it removes some power-user features: there’s no direct view of source HTML, and you can’t arbitrarily compare two past revisions — you compare a chosen past version with its predecessor. If your workflow relies heavily on granular revision comparisons or HTML-level inspection, test this new UI before depending on it.
Developer highlights
– PHP-only block registration: You can register blocks purely with PHP using register_block_type with autoRegister and a render_callback, avoiding a JS build step for simple server-rendered blocks.
– Pattern overrides for custom blocks: Pattern Overrides now work with any block that supports Block Bindings, not just a small set of core blocks. This helps client projects using bespoke blocks.
– Client-side Abilities API: A JavaScript counterpart to the server Abilities API split into @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected). The changes hint at future integrations with browser agents and extensions.
– Per-instance custom CSS: Blocks now offer a CSS input in the sidebar where you can write declarations directly (no selector needed) and use & for nesting — useful for targeted styling without editing theme CSS.
Design and content-editing improvements
– Navigation overlays: Better mobile navigation control with overlay template parts, four built-in patterns, an “always visible” toggle for submenus, and the ability to create pages from the Navigation block.
– Content-focused pattern editing: Patterns now default to a content-only mode that exposes editable text/image fields in a clean sidebar while preserving the layout. You can detach a pattern for full editing if needed — handy for client handoffs to avoid accidental structural edits.
– Viewport-based block visibility: You can show or hide any block per device (desktop, tablet, mobile) directly from the toolbar — a capability that previously often required plugins.
Command palette
A global Command Palette (⌘K / Ctrl+K) is available across the admin to quickly jump to settings and screens from anywhere.
Verdict
WordPress 7.0 is a solid, forward-looking release. Not every change is exciting to every user, but the overall direction is clear: core is becoming a neutral orchestration layer — particularly for AI — while improving collaboration and making editing more visual and approachable. The Connectors API and wp_ai_client_prompt() are likely to spawn interesting third-party features, and the RTC foundation could grow into a robust collaboration system.
Kudos to the contributors — there’s a lot to explore and build on. What stands out to you in 7.0? Anything here you’re excited to try or worried about?