WordPress 7.0 is one of the more consequential updates in recent years — not just a feature bump, but a clear statement about where WordPress wants to go next. The release is scheduled for May 20, 2026, and it brings a mix of collaboration features, AI infrastructure, editor polish, and developer conveniences. Here’s a straightforward look at what changed and what it means for different users.
1) Real-time collaboration (RTC)
What it is: WordPress now supports real-time editing of posts and pages. Multiple people can edit simultaneously and see each other’s changes as they happen. The system uses CRDTs (Conflict-free Replicated Data Types) for conflict resolution and relies on HTTP polling so it works across a wide range of hosts.
Important constraints:
- Initially limited to two simultaneous collaborators (a decision driven by hosting concerns).
- Hosts can replace transport/storage; developers can tweak polling intervals with JS filters.
- RTC is disabled when metaboxes are present — a hint that plugin authors should adapt how they add custom UI.
- After initial backlash, the feature is opt-in rather than enabled by default.
Who should care: This is primarily aimed at newsrooms, editorial teams, and enterprise setups where synchronous collaboration is useful. For many solo writers and small teams it may not be essential — and some writers will prefer the solitude of drafting offline. Still, this is a meaningful step toward a more collaborative WordPress editing experience and likely to evolve.
2) AI foundation: Connectors API + WP AI client
What it is: Rather than shipping a single “WordPress AI,” 7.0 introduces the plumbing to let plugins and themes integrate AI in a consistent, secure way.
Key pieces:
- A new Connectors screen in wp-admin where users add and manage API keys (OpenAI, Anthropic, Gemini, etc.).
- A Connectors API that plugins can use to request credentials and connect to external services — not limited to AI providers.
- A provider-agnostic PHP helper (wp_ai_client_prompt()) that sends prompts to an LLM without each plugin handling credentials directly.
Who should care: Developers will appreciate that WordPress handles credential management and provides a uniform interface to AI services. For site owners, this makes adopting AI-powered features easier and safer because credentials aren’t scattered across multiple plugin settings. WordPress is positioning itself as a neutral orchestration layer for AI rather than endorsing a single provider.
3) Visual revisions
What it is: Revisions are now integrated into the main post editor with a visual timeline and color-coded changes (yellow = modified, red = deleted, green = added). There’s a timeline slider in the header, a minimap on the scrollbar showing where changes occurred, and a Restore button when viewing past versions.
Trade-offs:
- The new UI is more accessible and less technical for many users.
- It shows rendered content rather than raw HTML, and you can’t directly compare any two arbitrary revisions; comparisons are limited to a selected version and its immediate predecessor.
Who should care: If you’re already using revisions, the new UI may or may not be an improvement depending on whether you valued the old revision viewer’s raw-diff and pairwise comparisons. For non-technical editors, the visual approach is easier to understand.
Developer standouts
- PHP-only block registration: You can now register blocks using only PHP (no JS build step). Using register_block_type with an autoRegister flag and a render_callback makes server-rendered, non-interactive blocks simple to create.
- Pattern overrides for custom blocks: Pattern Overrides now work with any block that supports Block Bindings, not just Heading/Paragraph/Button/Image. This is useful when using synced patterns but needing instance-specific content.
- Client-side Abilities API: A JavaScript counterpart to the server-side Abilities API (packages: @wordpress/abilities and @wordpress/core-abilities). This helps standardize capability checks in client code and hints at future agent/extension integrations.
- Custom CSS per block instance: Each block can now have custom CSS entered in the sidebar. You write declarations only (no selectors) and use & for nesting, which is handy for per-instance styling without custom classes.
Design and content editing wins
- Navigation overlays: Greater control over mobile menus, with built-in overlay patterns, submenu visibility toggles, and the ability to create pages from the Navigation block.
- Content-focused pattern editing: Patterns default to a content-only editing mode with streamlined sidebars so clients can edit content without breaking layouts; you can detach patterns for full control.
- Viewport-based block visibility: Show or hide blocks per device type (desktop/tablet/mobile) directly from the toolbar — a feature previously delivered by plugins.
Command Palette reminder
WordPress includes a global Command Palette, accessible with ⌘K / Ctrl+K, making it faster to find settings, tools, and commands from anywhere in the admin.
Verdict: Good, forward-looking release
Overall, WordPress 7.0 is a strong and coherent update. It’s not just incremental polish — it signals WordPress’ direction: more collaboration, native AI integration points, and smoother editing and theme-building UX. Some choices (RTC limits, revisions tradeoffs) are conservative or opinionated, but the platform is laying infrastructure that others can extend.
If you’re a developer, the AI connectors and PHP-only block registration are potentially huge time-savers. If you manage editorial teams, real-time editing may prove valuable as it matures. And for anyone building or handing off sites, content-focused patterns and per-block CSS help protect designs while keeping content editable.
What do you think of WordPress 7.0? Is there a feature here you’ll start using right away?
P.S. If you want practical performance tips, check out the crash course on speeding up WordPress — a few simple fixes can reduce loading times dramatically.
