Mike Herchel Outlines Drupal CMS and Canvas Direction at PHPverse 2026

Speaking at PHPverse 2026, Mike Herchel, a Drupal core subsystem maintainer, described Drupal CMS, Drupal Canvas, site templates, component architecture, workflow automation, caching, and AI-assisted site building as part of Drupal’s effort to reduce setup and adoption friction. JetBrains scheduled the session, “This Isn’t the Drupal You Remember,” for 14:25–14:55 UTC on 9 June 2026. A recording was later published on the PHP Annotated YouTube channel.

The talk was not a release announcement. Herchel framed Drupal’s current product work as a response to long-standing concerns about complexity, initial setup, page building, front-end implementation, and implementation cost. He also presented those changes to a wider PHP audience rather than only to Drupal site builders.

Herchel described Drupal CMS as an “easy button for Drupal” built on top of Drupal core. He said Drupal core now functions as the framework layer, while Drupal CMS packages preconfigured modules and best-practice defaults for common site needs. He also discussed site templates that can include sample content, dependencies, content types, fields, themes, YAML files, and composer.json files.

The most detailed demonstration centred on Drupal Canvas, the visual page-building project included with Drupal CMS. Herchel said Drupal Canvas lets content teams edit text in context, drag components, preview responsive layouts, and assemble landing pages in the browser. He positioned the editor as a way to shorten landing-page assembly without removing Drupal’s structured content model underneath.

On front-end architecture, Herchel connected Drupal Canvas to Single Directory Components and code components. He said Single Directory Components place a Twig template, CSS, JavaScript, and schema metadata in one component directory, allowing Drupal to understand the data a component expects. He described code components as JSX-based components stored as Drupal configuration, editable in the browser, previewable with CSS, and exportable for version control.

The session also connected the interface changes to Drupal’s PHP foundations. Herchel cited Drupal’s move to object-oriented PHP, Symfony components, Composer-based dependency management, dependency injection, PHP fibers, cache tags, cache contexts, internal reverse proxy caching, Dynamic Page Cache, BigPipe, and htmx. He said these changes support faster rendering and more responsive editorial workflows, while also referring to recent reductions in database queries in some cases.

Herchel also presented ECA, short for Event - Condition - Action, as a visual workflow tool for Drupal sites. He said ECA lets teams model event-driven processes, conditions, and actions in the browser. He also said those workflow models can be tested, exported, version-controlled, shared, and reused as starting points for more complex processes.

The AI portion of the talk focused on the Drupal AI Initiative and related base modules. Herchel said the initiative provides shared foundations for provider configuration, secure key handling, and modules that build on a common integration layer. He argued that Drupal’s structured content, governance model, object-oriented codebase, and API boundaries may make agentic workflows easier because agents struggle more with ambiguity than complexity.

The session remained a technical community overview, not an evidence-led market analysis. Herchel made claims about faster builds, lower project cost, and performance improvements, but the talk did not present independent benchmark data or adoption figures for those claims. Its main value is as a record of how Drupal CMS, Drupal Canvas, workflow automation, and AI work are being framed together in Drupal’s current product strategy.