WordPress 7.0 is shaping up to be one of the biggest shifts in what the platform aims to be. This release isn’t just adding features; it signals a reorientation toward collaboration, AI integration, and more visual content tools. Here’s a concise breakdown of what’s new and what it means for typical users and developers.

Release date: May 20, 2026.

1) Real-time collaboration (RTC)
The headline feature: multiple people can now edit the same post or page in real time, with edits appearing live for collaborators. The implementation details matter:
– Uses CRDTs (Conflict-free Replicated Data Types) to resolve concurrent edits.
– Built on HTTP polling so it will work across many hosts without specialized infrastructure.
– Initially limited to two simultaneous collaborators, a choice made to limit resource and hosting impacts.
– Hosts can swap transport/storage providers; developers can tweak polling via JS filters.
– RTC is disabled if metaboxes are present, signaling plugin authors to modernize integrations.

Should you care? Real-time editing is clearly aimed at enterprise teams and newsrooms. For solo writers or small teams it may be unnecessary or even intrusive — many authors prefer drafts untouched while composing. The feature is currently opt-in after some community pushback, and it’s only the first iteration. Expect evolution over the next year or two.

2) AI foundation: Connectors API + WP AI client
Rather than shipping a built-in “WordPress AI,” 7.0 provides the plumbing so others can build AI features consistently and securely. Key parts:
– A new Connectors screen in wp-admin to manage external API credentials (OpenAI, Anthropic, Google, etc.).
– Connectors API for plugins needing external service credentials; not limited to AI use cases.
– A provider-agnostic PHP function (wp_ai_client_prompt()) developers can call to send prompts to LLMs without handling provider-specific logic.

Should you care? If you’re a developer, yes — this makes building AI-powered features easier and more secure by centralizing credential handling and standardizing calls. For users, it keeps WordPress neutral: core doesn’t force a specific AI provider but enables an ecosystem of integrations.

3) Visual revisions
Revisions move from a separate screen to an inline, visual experience on the editor screen. Highlights:
– New timeline slider in the header to browse versions.
– Color-coded changes: yellow for modified, red for deleted, green for added.
– Minimap on the scrollbar showing where changes occur.
– A Restore button appears when you’re viewing older versions.

Should you care? The UI is friendlier for non-technical users, but it drops some of the old revision strengths: you no longer see raw HTML/source code and you can’t arbitrarily compare any two historical revisions — comparisons are against the immediately preceding version. Power users who rely on granular diffs might find the new approach limiting; casual users may appreciate the visual simplicity.

Developer standouts
– PHP-only block registration: You can now register blocks with PHP only (register_block_type with autoRegister and a render_callback), removing the need for a JS build step for simple server-rendered blocks.
– Pattern overrides for custom blocks: Synced patterns can now let specific content change per instance while keeping layout consistent, and support is expanded to any block using Block Bindings.
– Client-side Abilities API: A JS counterpart to the server-side abilities from 6.9, split into @wordpress/abilities (state) and @wordpress/core-abilities (REST-connected). This hints at future agent/extension integrations.
– Custom CSS per block instance: A CSS field appears in the block sidebar where you write declarations (no selectors) and use & for nesting — useful for per-instance styling without custom classes.

Design and content editing wins
– Navigation overlays: Better control for mobile hamburger menus, with built-in patterns, an always-visible submenu toggle, and the ability to create pages from the Navigation block.
– Content-focused pattern editing: Patterns now default to content-only mode with a clean sidebar showing editable fields — handy for client handoffs and preventing accidental layout changes.
– Viewport-based block visibility: Show or hide blocks per device type (desktop, tablet, mobile) directly from the toolbar. What used to require plugins is now in core.

Command Palette reminder
WordPress includes a Command Palette accessible with ⌘K / Ctrl+K that lets you jump to settings and editor actions from anywhere. It’s not new to 7.0, but it’s worth remembering as a fast navigation tool.

Verdict
Overall, this is a strong release. Some features (RTC and visual revisions) will spark debate about usefulness for everyday users, but the broader direction is sensible: WordPress positioning itself as a neutral orchestration layer for AI services, improving collaboration tools, and making editing and developer workflows smoother. The Connectors API and PHP-only block registration are especially promising for extending WordPress without reinventing credentials or build tooling.

What are you most excited (or worried) about in WordPress 7.0?

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.