Canvas vs Standard SDC Decision

When to Use

You are deciding whether to build a site with Drupal Canvas (the page builder) or with standard Drupal theming using SDC components, Layout Builder, or content types with Twig templates. This is an architectural decision made at project start.

Decision

If your project has...	Choose...	Why
Non-technical content editors who need to build pages	Canvas	Visual drag-and-drop; no Drupal knowledge needed
Marketing team managing landing pages	Canvas	Self-service page building; reduces developer bottleneck
A small, fixed set of page layouts	Standard theming	Layout Builder or templates are simpler for fixed layouts
Existing Paragraphs-heavy architecture	Standard theming (short-term)	Migration to Canvas is non-trivial
Component-library governance requirement	Canvas	All pages built from approved SDC/Code Components enforces design system
A headless/decoupled architecture	Evaluate carefully	Canvas decoupled is possible but complex (see Decoupled Frontend Patterns)
Budget for component library development	Canvas	Requires upfront investment building Canvas-compatible components
Pure developer-managed content	Standard theming	Canvas editorial features add no value if developers edit everything

Key Architectural Differences

Concern	Canvas	Standard SDC Theming
Page composition	Component tree stored in field	Twig templates + Layout Builder regions
Editor experience	Visual drag-and-drop with real-time preview	Drupal admin forms
Component authoring	SDC or React Code Components	SDC (Twig only)
Design enforcement	All pages must use defined components	Templates can be overridden; editors add free text
Drupal version	^11.3 required	Drupal 9+
Theming approach	Tailwind (Code) + CSS (SDC)	Bootstrap/any CSS framework
Existing contrib module integration	Still maturing (many modules not Canvas-aware yet)	Full contrib ecosystem compatibility

Pattern: Hybrid Approach

Canvas does not replace all Drupal content — it is targeted at landing pages, marketing pages, and editorial-built pages. A typical hybrid site:

Canvas pages: Homepage, campaign pages, landing pages, team/about pages
Standard content types: Blog posts, news articles, product catalog pages, documentation
SDC components: Used in BOTH contexts — Canvas uses them as page components; standard templates use them via {% include %}

This hybrid is the recommended approach for most sites. Develop SDC components that work in both contexts.

Common Mistakes

All-or-nothing thinking — most production sites will use Canvas for some content and standard Drupal for others
Rewriting existing SDC components into Code Components when they could stay as SDC — only convert if you need React interactivity
Choosing Canvas solely because it is new — evaluate against actual project requirements and editor personas
Not accounting for the component library investment — Canvas requires a library of Canvas-compatible components before editors can be productive