Drupal AI Development

Drupal CMS 2.0 and Canvas in a client project

Drupal CMS 2.0 promises a faster start, visual page building and AI-assisted workflows. In a client project, the important question is not only how good the demo looks, but how the solution behaves two years later.

Drupal CMS 2.0 was released on 28 January 2026. Its main themes are Canvas, AI tools and site templates. Drupal.org describes it as a way for marketing teams to launch branded sites faster.

This is an important shift for Drupal. Drupal has long been strong for complex systems, but getting started has often required more technical work than simpler CMS products. Drupal CMS is an attempt to reduce that friction.

What changed in Drupal CMS 2.0?

Drupal CMS 2.0 is not a separate technology branch. It is still Drupal, but with a new starting point.

The main changes include:

  • Canvas as a visual page building experience;
  • ready-made components and page sections;
  • site templates, including a marketing-site starting point;
  • AI-assisted tools for content and page creation;
  • faster initial setup for content-focused websites.

The Drupal CMS 2.0 release notes describe Canvas as the default editing experience with drag-and-drop, live preview and the Mercury component library.

Why this matters to clients

A client usually does not care whether the site uses Canvas, Layout Builder or Paragraphs. The important question is whether content can be managed quickly and safely.

Drupal CMS 2.0 can help when:

  • the project is mostly a marketing or content site;
  • editors need to create campaign pages themselves;
  • the design is based on reusable sections;
  • time to first launch matters;
  • there are few complex integrations.

In that situation, a ready-made starting point can reduce analysis and configuration work.

Where the risk starts

Visual page building becomes risky when it gives editors too much freedom without a system.

Common problems include:

  • every page starts looking different;
  • components duplicate each other;
  • accessibility depends on editor discipline;
  • brand consistency weakens;
  • performance suffers because pages become heavy;
  • developers later cannot tell what belongs to the design system and what is a one-off exception.

Canvas should therefore not be judged only by how quickly a demo can be built. Control, reuse and maintainability matter just as much.

Canvas does not replace architecture

Drupal CMS 2.0 can make page assembly easier, but it does not decide:

  • the content model;
  • permissions;
  • translation workflow;
  • SEO architecture;
  • integration logic;
  • test coverage;
  • publishing workflow;
  • maintenance process.

If those decisions are skipped, the result is simply a more modern-looking mess.

A solid client project still needs a technical owner who decides what belongs in a component, what belongs in a content type, what belongs in configuration and what needs custom development.

When Drupal CMS 2.0 fits

Drupal CMS 2.0 can be a good choice when:

  • the goal is to launch a content-focused website quickly;
  • the site is not a complex information system;
  • editors need flexible landing pages;
  • the organisation wants Drupal without large custom development at the start;
  • future growth inside the Drupal ecosystem is still important.

It may be especially interesting for organisations comparing WordPress or Webflow, but needing stronger long-term control over permissions, multilingual content and structured data.

When to be careful

Be more cautious when:

  • the project depends on complex integrations;
  • business logic is specific;
  • the design system is already strict;
  • the website is part of a larger portal;
  • there are many content types and workflows;
  • development must fit into an existing Drupal platform.

In those cases, a standard Drupal architecture may still be the better starting point, even if some Drupal CMS 2.0 ideas are adopted.

AI tools must not make the decisions

The AI direction in Drupal CMS 2.0 is interesting, but a client project needs clear boundaries.

AI can help:

  • draft first-pass content;
  • suggest SEO titles;
  • create a rough page section;
  • help editors find structure;
  • speed up repetitive content work.

AI should not independently decide:

  • legally important text;
  • accessibility compliance;
  • brand voice;
  • technical architecture;
  • publishing without human review.

The same principle applies to other AI-assisted Drupal work: AI is an assistant, not the responsible party.

How to decide

Before choosing Drupal CMS 2.0, answer a few questions:

  1. Is the project mainly a content site or an information system?
  2. How much layout freedom do editors need?
  3. How strict must the design system be?
  4. Are integrations likely to appear later?
  5. Must accessibility and performance be covered by tests?
  6. Who owns component quality after launch?

If the answers point to a fast but controlled content-site starting point, Drupal CMS 2.0 may be a good fit. If the answers point to a complex platform, start with Drupal development analysis and choose the architecture from there.

Short conclusion

Drupal CMS 2.0 makes Drupal more attractive for projects where the first setup used to feel too heavy. Canvas and site templates reduce the blank-page problem.

In a client project, the question is not only whether the tool is new. The question is whether the starting point supports content management, accessibility, performance, testing and maintenance after launch.

WebPro can help assess whether Drupal CMS 2.0 is the right starting point for a specific project or whether a standard Drupal architecture would be safer.

Subscribe via RSS
Kaido Toomingas Kaido Toomingas WebPro Company OÜ

Need Drupal help?

If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.

Contact us