No Single Builder Defines Drupal’s Site-Building Path

Site builders currently face several Drupal interfaces without a settled long-term standard, according to Rod Martin of Drupal Helps. In Drupal’s Site-Building Direction Isn’t Settled Yet. Here’s How to Build Anyway, Rod reviews Layout Builder, Paragraphs, Drupal Canvas, UI Patterns, and Display Builder, arguing that teams should treat the selected builder as a replaceable layer rather than allowing it to determine the entire content and component architecture. His analysis places the more durable architectural choices in structured content and reusable components rather than in any one page-building interface.

The distinction matters because the tools do not share the same project status or role in Drupal’s product strategy. The Drupal Core strategy defines Core as the platform for building customised CMS solutions, while Drupal CMS 2.0 uses Canvas as its default editing experience. Single-Directory Components have been part of Core’s render system since Drupal 10.3, while Display Builder remains in beta with no supported stable release.

Rod recommends keeping meaningful content in fields and entities, building frontend components with SDC, and selecting one primary builder for each project. A Drupal Core reconciliation issue records discussion about overlapping responsibilities among Block Layout, Layout Builder, and Canvas. The issue includes proposals to move Layout Builder overrides, and potentially more of Layout Builder, to contrib, but it does not establish an approved removal or migration plan. Rod presents the portability guidance as practitioner analysis and explicitly notes that he has not used Paragraphs on a production project.