WordPress 7.0 feels like a turning point — either a major evolution or a bold redefinition of what WordPress aims to be. Instead of merely iterating on the publishing flow we’ve known for years, this release signals a shift in priorities and intended users.
Release status
Current planned release date: May 20, 2026.
What’s new and why it matters
1) Real-time collaboration (RTC)
The marquee feature: multiple people can edit the same post or page at the same time and see edits live, much like Google Docs. Technical notes: it uses CRDTs for conflict resolution, operates over HTTP polling for broad hosting compatibility, and initially limits sessions to two simultaneous collaborators to reduce host load. Hosts can plug in their own transport and storage, and developers can tune polling via JS filters. Important: RTC is disabled when metaboxes are present, signaling plugin authors to adapt how they add UI.
Who benefits? This is clearly aimed at larger teams — newsrooms, editorial teams, or enterprise setups. For many solo writers or small teams it may feel unnecessary (and intrusive if you prefer uninterrupted drafts). The feature was intended to be enabled by default but is now opt-in after community feedback. Expect this to evolve over time.
2) AI foundation: Connectors API and WP AI client
Rather than baked-in AI features, 7.0 provides the plumbing so plugins and themes can connect to external AI services safely and consistently. The changes include a new Connectors screen in wp-admin for managing provider credentials (OpenAI, Anthropic, Gemini, etc.), a Connectors API plugins can use to manage external connections, and a provider-agnostic PHP helper (wp_ai_client_prompt()) to send prompts to an LLM.
Why it matters: this makes it much easier for developers to add AI capabilities without reimplementing credential handling or provider logic. WordPress positions itself as a neutral orchestration layer for AI rather than shipping a single WordPress-branded model. For devs building AI integrations, this is a smart and useful foundation.
3) Visual revisions
The revisions UI is now integrated into the editor and focuses on a visual comparison of changes. New tools include a timeline slider for moving through versions, color-coded edits (yellow = modified, red = removed, green = added), a minimap on the scrollbar to jump to changed areas, and a Restore button when viewing history.
Trade-offs: the new view is more approachable for non-developers, but it omits a few things power users liked: you don’t see the raw HTML source and you can’t arbitrarily compare any two historical revisions — the UI compares a selected past version to its immediate predecessor. Worth testing to see if the visual approach fits your workflow.
Developer highlights
– PHP-only block registration: You can now register blocks purely in PHP (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 expand beyond a few core block types to any block that supports Block Bindings, so synced patterns can keep layout while letting instance content vary.
– Client-side Abilities API: A JavaScript counterpart to the server-side Abilities API landed, split into @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected), paving the way for browser agents, extensions, and agent integrations.
– Custom CSS per block instance: Blocks now get a CSS field in the sidebar where authors can write declarations (no selectors needed) and use & for nesting — handy for small styling tweaks without theme edits.
Design and content-editing wins
– Navigation overlays: Greater control over mobile menus via overlay template parts, multiple 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 so editors see a simplified interface to change text and images without exposing the full block tree. You can detach patterns to gain full control when needed — useful for client handoffs to prevent accidental layout changes.
– Viewport-based block visibility: Show or hide blocks per device (desktop/tablet/mobile) from the toolbar — functionality many plugins previously provided is now in core.
Command palette reminder
WordPress includes a global Command Palette (invoke with ⌘K / Ctrl+K) to quickly find settings and actions from anywhere in the admin.
Verdict: a solid release
Overall, 7.0 is a strong release that clarifies WordPress’s direction: more collaborative workflows, a neutral AI integration layer, and continued refinement of the block editor and developer APIs. Not every addition will excite every user — RTC is niche at present and the visual revisions trade off some power-user features — but the connector strategy for AI and the developer-focused enhancements are likely to have long-term impact.
I’m especially interested to see what people build on top of the Connectors API. Positioning WordPress as an orchestration point for external AI services feels like a pragmatic, future-facing move.
What do you think? Is there a feature here you’re most excited to try?
P.S. If you want to speed up your WordPress site, we run a crash course that covers simple fixes that can cut load times dramatically (often 50–80%). Signing up adds you to a weekly newsletter and you can unsubscribe anytime.