WordPress 7.0 is being billed as one of the most meaningful updates in years — or, depending on how you look at it, the boldest redefinition yet of what WordPress intends to be. Instead of incremental tweaks, this release pushes toward collaborative editing and AI integration while polishing editing and developer workflows.
Release date
Current release date for WordPress 7.0: May 20th, 2026.
1) Real-time collaboration (RTC)
The headline feature is real-time collaboration: multiple people can now edit the same post or page and see changes as they happen. It’s conceptually similar to Google Docs but with some WordPress-specific constraints.
Key details:
– Uses CRDTs (Conflict-free Replicated Data Types) for conflict resolution.
– Built on HTTP polling so it can work across a wide range of hosts.
– Initially limited to two simultaneous collaborators to protect hosting resources.
– Hosts can provide alternative transport or storage; developers can tweak polling via JS filters.
– Collaboration is disabled when metaboxes are present, nudging plugin authors toward modern patterns.
Should you care? This is most useful for enterprise teams and larger newsrooms. For solo authors or small teams it may be less compelling — many writers prefer to work on drafts alone. The feature was originally intended to be on by default but is now opt-in after community feedback. It’s early-stage and likely to expand in future releases.
2) AI foundation: Connectors API + WP AI client
Rather than shipping built-in AI features, WordPress 7.0 provides the framework for AI integrations so third-party plugins and tools can plug in easily.
What’s included:
– A new Connectors admin screen to manage API keys for services like OpenAI, Anthropic, Gemini, etc.
– A Connectors API plugins can use to access external services without each plugin reinventing credential handling.
– A provider-agnostic helper, wp_ai_client_prompt(), for sending prompts to an LLM from PHP.
Should you care? If you’re a developer building AI-powered features, this is huge: it centralizes credential management and lets different plugins use the same, neutral plumbing. WordPress is positioning itself as an orchestration layer rather than shipping a single “WordPress AI” product, which keeps options open and encourages ecosystem innovation.
3) Visual revisions
The classic revisions UI gets a rework and is now integrated into the main post-editing screen with a more visual, color-coded interface.
What’s new:
– Timeline slider in the editor header to jump between versions.
– Color coding: yellow for modified, red for deleted, green for added.
– A scrollbar minimap highlighting where changes appear.
– “Restore” becomes available while browsing history (replacing the old publish workflow during review).
Caveats: The new revisions view shows rendered content rather than raw source (no HTML view), and you can’t pick arbitrary pairwise revisions to compare — you can only compare a selected past version to its direct predecessor. For long-time users of the old revisions screen, that might feel like a loss; for non-technical users, it’s likely more approachable.
Developer standouts
– PHP-only block registration: You can now register blocks using only PHP (no JavaScript build step). Use register_block_type with autoRegister and a render_callback for server-rendered blocks and basic sidebar controls generated automatically.
– Pattern overrides for custom blocks: Pattern overrides now work for any block that supports Block Bindings, not just a handful of core blocks. This helps when you want consistent layouts with instance-specific content.
– Client-side Abilities API: A JavaScript counterpart to the server-side Abilities API shipped in 6.9. It includes @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected) and hints at future browser agents, extensions, and AI interoperability.
– Custom CSS per block instance: There’s a CSS field in the block sidebar. You enter declarations only (no selectors), and you can use & for nesting — handy for quick styling without editing theme files.
Design and content editing wins
– Navigation overlays: Improved control for mobile hamburger menus with overlay template parts, multiple built-in patterns, a toggle for always-visible submenus, and the ability to create pages from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only mode showing editable fields in a simplified sidebar rather than the full block tree. You can detach the pattern to edit the full structure if needed. This is useful for client handoffs where you want to limit accidental layout changes.
– Viewport-based block visibility: You can now show or hide blocks by device (desktop, tablet, mobile) from the toolbar — functionality that previously required plugins.
Command Palette reminder
WordPress includes a global Command Palette accessible with ⌘K / Ctrl+K. It lets you quickly find settings, blocks, and options from anywhere in the editor.
Verdict: good release
Overall, 7.0 is a strong release. Not every feature will excite every user — some changes target enterprise workflows or developers — but the direction is clear. WordPress is embracing collaboration and enabling AI integrations while continuing to refine editing and developer ergonomics.
The AI connectors are the most forward-looking element: rather than picking a platform, WordPress supplies the neutral infrastructure for others to build on. If you’re a developer or run a team that will benefit from real-time editing, this release matters. If you’re mainly a solo blogger, many improvements are nice-to-have for now.
What do you think about WordPress 7.0? Any feature you’re most interested in?
Bonus: Speed-up course
There’s a crash course available on speeding up WordPress sites — simple fixes can often cut load times by 50–80%. By subscribing with your email you’ll receive weekly updates and tips; you can unsubscribe any time.
