WordPress 7.0 is one of the most consequential updates in years — not just a set of incremental tweaks, but a clear reframing of what WordPress wants to be. This release leans into collaboration, infrastructure for AI, and a number of editor and developer quality-of-life improvements. Below is a practical run-down of what changed and why it matters for different users.
Release date
Current stable release date: May 20, 2026.
1) Real-time collaboration (RTC)
The headline feature is real-time collaborative editing: multiple people can edit the same post or page and see edits as they happen, similar to Google Docs.
Key technical details:
– Uses CRDTs (Conflict-free Replicated Data Types) for conflict resolution.
– Uses HTTP polling as the transport to maximize host compatibility.
– Initially limited to two simultaneous collaborators per document to reduce server strain.
– Hosts can supply their own transport and storage; JS filters allow developers to tweak polling.
– RTC is disabled if legacy metaboxes are present, which pushes plugin authors toward more modern implementations.
Who should care?
This is most useful for newsrooms, editorial teams, and enterprise setups. Solo writers and small teams may find it unnecessary or intrusive. RTC was intended to be on by default but is now opt-in after feedback; expect this to evolve across future releases.
2) AI foundation: Connectors API + wp_ai_client
Instead of shipping a single WordPress-branded AI, 7.0 provides the plumbing so third-party plugins and services can plug in easily.
What’s included:
– A new Connectors screen in wp-admin to manage API keys for providers like OpenAI, Anthropic, Google, etc.
– A Connectors API that standardizes how plugins request external credentials (useful beyond AI).
– A provider-agnostic PHP helper function (wp_ai_client_prompt()) that sends prompts to registered LLMs.
Why this matters:
It’s smart architecture. WordPress becomes an orchestration layer that lets sites connect to multiple AI providers without each plugin reimplementing credential management. Developers can build AI features faster and more securely, and site owners retain choice over providers.
3) Visual revisions
Revisions have been integrated into the main editor with a visual, color-coded interface.
Notable UX changes:
– A timeline slider in the editor header to scrub through versions.
– Color codes to indicate changes: yellow = modified, red = deleted, green = added.
– A minimap on the scrollbar showing where edits occurred.
– When viewing history, a “Restore” button replaces “Publish.”
Trade-offs:
This makes revision history far more approachable for editors, but power users lose some legacy features: you don’t get raw HTML diffs and you can’t arbitrarily compare any two revisions (you compare a chosen past state to its immediate predecessor). Try it to see if the simplified workflow suits you.
Developer standouts
– PHP-only block registration: You can now create simple blocks using only PHP (call register_block_type with autoRegister and provide a render_callback) without a JS build step. Great for server-rendered, low-maintenance blocks.
– Pattern overrides for custom blocks: Synced patterns can include instance-specific content while preserving layout. Any block supporting Block Bindings can use Pattern Overrides — handy for client projects and templated content.
– Client-side Abilities API: The JavaScript complement to the server-side Abilities API introduced in 6.9. Packages include @wordpress/abilities (state) and @wordpress/core-abilities (REST-backed). Mentions of browser agents and WebMCP suggest further AI/agent interoperability down the road.
– Custom CSS per block instance: Authors can add declarations (no selectors) directly in a block’s sidebar. Nesting using & is supported for scoped styling.
Design and content editing wins
– Navigation overlays: Better control over mobile hamburger menus, with customizable overlay template parts, built-in patterns, a toggle for always-visible submenus, and the ability to create pages directly from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only editing mode (editable fields in a clean sidebar while preserving layout). You can detach when you need to fully edit structure — ideal for handing sites to clients.
– Viewport-based block visibility: You can show/hide any block per device type (desktop, tablet, mobile) from the toolbar — something that previously required plugins.
Command Palette
A system-wide Command Palette is available anywhere via ⌘K / Ctrl+K for quick access to settings, actions, and navigation.
Verdict: good and directional
This is a strong release. Some features — especially RTC — feel targeted at larger organizations and will be niche for many users initially. More consequential is the platform-level AI infrastructure: WordPress is choosing to be a neutral connector and orchestration layer rather than shipping a single AI product. That’s a pragmatic approach that should help the ecosystem move faster and give site owners more choice.
Overall, 7.0 delivers meaningful editor and developer improvements while laying the groundwork for broader AI integrations. I’m most curious to see what plugins and services build on the new Connectors API and how collaborative editing matures.
What do you think of WordPress 7.0? Any features you’re excited to try?
Quick note: Want faster load times? Small optimizations can often cut WordPress page load by 50–80%.
By entering your email on the site you’ll subscribe to the weekly newsletter. You can unsubscribe anytime; the team respects your inbox and privacy.