WordPress 7.0 feels like one of the boldest updates in years — a statement about where WordPress wants to go: real-time collaboration, an AI integration layer, and a more visual revisions workflow. Below is a concise breakdown of what’s new and what it means for different users.
Status
Release date: May 20, 2026.
1) Real-time collaboration (RTC)
– What it does: Multiple people can edit the same post or page simultaneously and see live updates, similar to Google Docs.
– Key technical choices: CRDTs (Conflict-free Replicated Data Types) for conflict resolution; HTTP polling as the default transport so it works across varied hosts.
– Limits & customization: Initially capped at two simultaneous collaborators to reduce host load. Hosts can replace the transport/storage layer, and developers can tweak polling via JavaScript filters.
– Compatibility note: RTC is disabled when metaboxes are present, signaling plugin authors to update for compatibility. It was planned to be on by default but is opt-in after feedback.
– Who should care: Primarily teams, newsrooms, and collaborative shops. Solo bloggers may find live edits disruptive for drafts, but this is an early step that could broaden over time.
2) AI foundation (Connectors API + WP AI client)
– Approach: Instead of shipping built-in AI features, core provides the plumbing so plugins and themes can safely integrate AI providers.
– Components: A Connectors admin screen to manage API keys (OpenAI, Anthropic, Google, etc.), a Connectors API for plugins, and a provider-agnostic PHP helper (wp_ai_client_prompt()) to send prompts without wiring each provider.
– Why it matters: WordPress stays neutral — it won’t lock you into a single LLM vendor. Developers get consistent credential handling and a unified prompt API, making integrations easier and safer.
3) Visual revisions
– What’s new: Revisions now live in the post editor with a visual, color-coded timeline (yellow = modified, red = deleted, green = added), a header slider to browse versions, a scrollbar minimap, and an inline Restore action.
– Tradeoffs: The UI is friendlier for casual users but drops some power features from the classic revisions screen — no raw HTML/source view and you can only compare a chosen revision to its immediate predecessor rather than any arbitrary pair.
– Who benefits: Editors and non-technical users will like the clarity; power users who relied on deep comparisons may miss the old tools.
Developer standouts
– PHP-only block registration: register_block_type supports autoRegister + render_callback so simple server-rendered blocks can avoid a JS build step.
– Pattern overrides for custom blocks: Blocks that support Block Bindings can now be part of pattern overrides, useful for standardized layouts with instance-specific content.
– Client-side Abilities API: New JS packages (@wordpress/abilities and @wordpress/core-abilities) enable client-side capability checks and open doors for future agent/extension patterns.
– Custom CSS per block instance: A CSS field in the block sidebar accepts declarations (use & for nesting) so you can style a block instance without writing external selectors.
Design and content-editing wins
– Navigation overlays: Improved control for mobile menus with overlay template parts, built-in patterns, submenu visibility toggles, and the ability to create pages directly from the Navigation block.
– Pattern editing focused on content: Patterns default to a content-only mode with simple editable fields in the sidebar; you can “detach” a pattern when full control is needed — useful for client handoffs.
– Viewport-based block visibility: Toggle block visibility by device (desktop/tablet/mobile) from the toolbar — functionality many sites needed plugins to get before.
Command Palette
A system-wide Command Palette is now available — press ⌘K / Ctrl+K to quickly find settings and commands anywhere in the admin.
Verdict
Overall, 7.0 is a strong, directional release. Not every feature will excite every user, but the combination of collaboration, neutral AI orchestration, and a friendlier editing experience marks a clear strategy shift. The Connectors API is particularly promising because it makes WordPress a platform for AI integrations without endorsing a single provider. Expect interesting plugins and workflows to surface on top of these foundations.
What do you think of WordPress 7.0? Is anything here useful for your workflow?
Bonus: How to Speed Up Your WordPress Site
A short guide linked in the original post claims easy wins that often cut load times by 50–80%. Subscribing with your email signs you up for a weekly newsletter; you can unsubscribe anytime.