Release date
May 20, 2026
Quick overview
WordPress 7.0 is less about incremental polish and more about positioning: collaboration, an AI integration foundation, and friendlier visual tools. Many features are scaffolding for future workflows rather than finished consumer-facing products. Below is a practical rundown of what changed, how it works, and who should care.
1) Real-time collaboration (RTC)
What it does: Multiple people can edit the same post or page and see edits live, similar to Google Docs.
How it works: Uses CRDTs (Conflict-free Replicated Data Types) for conflict resolution and falls back to HTTP polling to maximize compatibility with a wide range of hosts.
Limits and controls:
– Initially limited to two simultaneous collaborators to reduce host load.
– Hosts can supply their own transport/storage; JavaScript filters let developers tune polling intervals.
– RTC is automatically disabled if metaboxes are present, so plugin authors will need to adapt integrations.
Who should care: Primarily enterprise teams and newsrooms. Solo writers or small teams may not need simultaneous editing yet, but this is an early step that can evolve.
2) An AI foundation (Connectors API + wp_ai_client)
What it does: Instead of shipping specific AI features, WordPress provides infrastructure to connect to AI providers.
Key pieces:
– New Connectors screen in wp-admin to add and manage API keys (OpenAI, Anthropic/Claude, Gemini, etc.).
– Connectors API that plugins can use to abstract provider credentials and behavior.
– wp_ai_client_prompt(): a provider-agnostic PHP helper for sending prompts to LLMs.
Why it matters: Developers can build AI features without each plugin reimplementing credential storage and provider differences. WordPress is positioning itself as a neutral orchestration layer for AI services rather than picking a single vendor.
3) Visual revisions
What’s new: Revisions are now visible directly inside the editor via a color-coded, timeline-based UI.
UI highlights:
– Timeline slider in the editor header for navigating versions.
– Color coding: yellow = modified, red = deleted, green = added.
– Minimap on the scrollbar showing where changes happened.
– Restore button available when browsing history.
Limitations to know:
– You see rendered content, not raw HTML diffs.
– You can compare a revision only with its immediate predecessor, not arbitrary pairs.
Who should care: Non-developers will appreciate the visual clarity. Power users who relied on HTML diffs and arbitrary comparisons may find the new UX less flexible.
Developer-focused changes
– PHP-only block registration: You can register and render blocks purely in PHP (no JS build step) by using register_block_type with autoRegister and a render_callback — good for server-rendered, non-interactive blocks.
– Pattern overrides for custom blocks: Synced patterns are more flexible; per-instance content changes are allowed across block types that support Block Bindings, which helps templating and client handoffs.
– Client-side Abilities API: A JS counterpart to server Abilities API is available (@wordpress/abilities and @wordpress/core-abilities) and is a hint toward richer client-side capability checks or future agent/AI integrations.
– Custom CSS per block instance: You can add CSS declarations in the block sidebar (no selector needed; use & for nesting). This makes quick, local styling easier without touching theme CSS files.
Design and content editing wins
– Navigation overlays: Better control over mobile hamburger menus with overlay template parts, built-in patterns, an “always visible” submenu toggle, and the ability to create pages from the Navigation block.
– Content-first pattern editing: Patterns default to content-only mode where text/image fields are editable in a clean sidebar while layout remains locked. You can detach if you need full control — useful for client handoffs.
– Viewport-based block visibility: Toggle block visibility for desktop, tablet, and mobile directly from the toolbar, a feature that previously needed a plugin.
Command Palette
A system-wide Command Palette (⌘K / Ctrl+K) is available from anywhere in the admin for quick access to settings and actions.
Verdict: Good direction, with caveats
Overall this is a strategic release with clear direction. RTC is promising but aimed at specific workflows; its initial limits make sense to ensure stability. The AI connectors are the most significant long-term change: by standardizing credential handling and provider abstraction, WordPress makes it easier for plugin authors to build AI experiences without reinventing the plumbing.
The visual revisions and content-focused editor improvements benefit non-technical users, although power users may miss raw HTML diffs and more flexible comparison tools.
What to watch next
– How developers and plugin authors adopt the Connectors API and build AI experiences on top of it.
– Whether RTC scales beyond two collaborators and how transport/storage options evolve.
– Whether revision UX adds arbitrary comparisons or a raw-diff view for power users.
Your turn
Do any of these features change how you’d use WordPress? What are you most excited or worried about in 7.0?