Web Development

Drupal CMS 2.0 and WordPress 7.0: What AI and Collaborative Editing Mean for Your Website

What actually shipped in both releases, what is still on the roadmap, and how to govern AI features and plan your upgrade.

Illustration of a team collaborating on content at laptops, reflecting collaborative editing in Drupal and WordPress

By DESSS Web Engineering Team

Drupal CMS 2.0, released January 28, 2026, made the Canvas visual builder the default and added optional AI tools for page generation and alt text. WordPress 7.0, released May 20, 2026, added an AI Client in core, but real-time collaborative editing was removed before launch and remains in development.

Both major open-source CMS projects shipped headline releases in 2026, and both put AI front and center. The marketing around them has been louder than the details, so this post sticks to what the official project sites say. For help deciding what these changes mean for your platform, see our CMS consulting and advisory services. For scale, W3Techs (read November 2026) reports WordPress on 39.3 percent of all websites and Drupal on 0.6 percent.

What Is New in Drupal CMS 2.0?

Drupal CMS 2.0 is the second major version of Drupal's ready-to-use package for marketers, released on January 28, 2026, according to Drupal.org. It makes Drupal Canvas, a drag-and-drop visual page builder, the default editing experience and adds optional AI tools on top of Drupal core 11.3.

According to the Drupal.org announcement and release notes, version 2.0 includes:

Drupal Canvas as the default editor, with live preview and the Mercury component library of cards, heroes, menus and accordions
Byte, the first site template, a preconfigured marketing site for a software product
Optional AI features, including page generation from text prompts, an admin chatbot for site-building tasks and alt text generation that keeps human review
An AI dashboard showing available features and configured providers, with a trial through amazee.ai or your own OpenAI or Anthropic keys

Existing sites are not forced to change. The release notes say a Drupal CMS 1.x site is a standard Drupal site you update as usual. Canvas can be added later, but it needs a component-based theme, and recipes have no update path. Drupal.org's release list already shows 2.1 and 2.2 versions since then. Our Drupal consulting page covers upgrades and Canvas adoption.

What Did WordPress 7.0 Ship?

WordPress 7.0, code-named Armstrong, was released on May 20, 2026, according to WordPress.org. Its main AI change is an AI Client in core that lets WordPress talk to generative AI models, paired with the Abilities API, plus a Connectors screen for managing external services.

Other changes listed in the release announcement:

A redesigned admin with a command palette opened by Ctrl+K or Cmd+K
Visual revision browsing with one-click restore
New Breadcrumbs and Icons blocks, and per-device visibility controls for blocks
Block-level custom CSS inside posts and pages

AI writing features, such as title and excerpt suggestions, image generation and alt text suggestions, come from a separately installed AI plugin, not core itself. WordPress 7.1, released August 19, 2026, followed with further Abilities API work.

Is Real-Time Collaborative Editing in WordPress 7.0?

No. Real-time collaborative editing was removed from WordPress 7.0 shortly before launch. A May 8, 2026 post on the Make WordPress Core blog said the approach was not yet robust enough, citing race conditions, server load, memory use and bugs found in testing.

A September 18, 2026 Core post describes a new server-aware approach, where WordPress itself acts as the authority for merging edits. The team is prototyping three sync engines, plans to ship the chosen one as a feature plugin for testing first and gives no release date.

What editors can use today is asynchronous feedback. Notes arrived in WordPress 6.9 for comments on individual blocks, and WordPress 7.1 added mentions, notes on specific text and multiple conversations per block.

Person facing a glowing AI neural network visualization, representing AI features now built into CMS platforms

What Changes for Site Owners and Editors

Drupal sites gain a visual builder that marketers can use without a developer, but only after a theme built for components is in place.
WordPress sites get a refreshed admin that will need brief retraining, plus an AI foundation that does nothing until a plugin and provider are connected.
Both platforms now treat AI as an opt-in layer, which means your organization, not the CMS, decides what is switched on.
Hosting teams should watch the collaboration work. The September Core post notes that frequent polling is costly and may be impractical on lower-resourced hosts, so live co-editing may need more server capacity when it arrives.

How Should You Govern AI Features in a CMS?

Govern CMS AI features by deciding who may enable them, which provider receives your content and which outputs need human approval before publishing. Treat the AI connection like any other third-party data processor, with a named owner, documented keys and a periodic review.

A practical policy covers:

Which roles may install AI plugins or add provider keys
What content may be sent to a provider, especially regulated health or customer data
Human review for anything published, including generated alt text
Where API keys are stored and how they are rotated
How AI-assisted content is labeled internally for audit

For Houston healthcare organizations around the Texas Medical Center, and energy companies handling operational data, the second item matters most. Read the provider's data terms before any editor connects a key, and keep regulated content out of prompts unless your compliance team has approved the arrangement.

Upgrade Planning

Inventory your version, themes, plugins or modules, and custom code.
Check compatibility notes from each vendor before upgrading.
Upgrade a staging copy first and test editor workflows, forms and search.
Take a verified backup and agree on a rollback point.
Leave AI features off until the governance policy is signed off.
Train editors on the new admin or Canvas before launch.

Our WordPress consulting services include staged upgrades of this kind. If the release has you questioning the platform altogether, read our comparison of headless CMS and WordPress first.

Key takeaways

Drupal CMS 2.0 shipped in January 2026 with Canvas and optional AI tools.
WordPress 7.0 shipped in May 2026 with an AI Client in core.
Real-time co-editing in WordPress is still in development with no date.
Set an AI policy before anyone connects a provider.

Frequently Asked Questions

Do I have to use AI if I upgrade to Drupal CMS 2.0 or WordPress 7.0?

No. Drupal.org describes the AI features in Drupal CMS 2.0 as optional, configured through an add-on, and WordPress 7.0 provides an AI foundation that needs a separate plugin and a connected provider before editors see AI tools. You can upgrade for the security fixes and editor improvements and switch AI on later, once a policy is agreed.

Can several people edit the same WordPress page at the same time?

Not in core today. Real-time collaborative editing was removed from WordPress 7.0 before release, and a September 2026 Core post says a new approach is still being prototyped with no release date. Editors can leave block-level Notes, which WordPress 7.1 extended with mentions and notes on specific text, but simultaneous live editing is not available yet.

Does my existing Drupal site have to move to Drupal CMS 2.0?

No. According to the release notes, a site built with an earlier Drupal CMS version is a standard Drupal site that you keep updating as usual. Drupal CMS is a starting point for new sites. You can add Canvas to an existing site later, but it requires a component-based theme, and recipes do not have update paths.

Which AI providers work with Drupal CMS 2.0?

The Drupal.org announcement lists a trial through the amazee.ai private AI provider plus support for OpenAI and Anthropic keys. Before connecting any of them, decide what content may be sent, where keys are stored and who approves generated output. Those choices matter more for risk than which provider you pick, especially for regulated or confidential data.

Plan Your Next Release With DESSS

Whether you are adopting Canvas, testing WordPress AI features or writing an AI policy for editors, a short review now prevents rework later. Contact DESSS at 2825 Wilcrest Dr #608, Houston, TX 77042; +1-713-589-6496; info@desss.com.