Canvas 1.0 shipped, and what it means for Drupal builders

Canvas 1.0 is live. The composition layer for Drupal is production-ready.

Canvas changes how Drupal handles page composition. Instead of Layout Builder blocks or custom Twig templates, editors compose pages using components and interactions. A card with a click handler. A hero with a parallax background. A grid that responds to viewport changes. The composition happens in the UI, not in code.

The beta cycle stabilised the interaction model. Components declare what they support. Editors use those declarations to compose pages. The markup stays clean. Accessibility is built in. Performance is handled.

For institutions using Drupal, this is the moment to evaluate. Canvas is no longer experimental. Platforms launching now can build composition workflows that would have taken weeks to develop as custom code. Existing platforms can migrate to Canvas incrementally.

What’s stable

Interaction handlers for navigation, modals, and scroll effects are solid. Component schemas work cleanly with Canvas. The accessibility layer passes WCAG compliance. The query API for canvas-defined pages is stable and usable.

The admin UI for composing pages is intuitive. Editors can build pages by clicking without technical training. The experience is closer to Figma than to Layout Builder.

What to watch

Conditional interactions are not supported yet. If your page needs an interaction that changes based on user state or content, that is custom code, not Canvas.

Progressive enhancement for sites without JavaScript is partial. Simple interactions degrade gracefully. Complex ones do not.

Performance at scale is still being tested. Platforms with hundreds of Canvas-composed pages are watching for query overhead and render time.

What to do now

If you are building a new Drupal site, Canvas is the composition layer to use. The learning curve is smaller than Layout Builder, and the results are more flexible.

If you are maintaining an existing platform, Canvas adoption is optional but worth evaluating. The migration path from Layout Builder to Canvas exists but is manual. Plan for that if you are considering a shift.

If you have custom composition code, Canvas does not replace all of it yet. Use Canvas for what it does. Keep custom code for what it does not. The two coexist.

Canvas is production-ready. The Drupal community has delivered a composition system that works. Use it.