Decoupled workflow capabilities are reaching milestone maturity within the enterprise market. With Drupal 11, the visual, component-based page building introduced by the Experience Builder initiative (now developed as Drupal Canvas) changes how editors and engineers collaborate on layouts.
The modern layout paradigm shift
For several release cycles, editing in traditional web platforms felt rigid, pushing structural component decisions down to custom module builders or deeply integrated layouts. The new engine changes this approach by exposing component properties directly in a visual design canvas. Editors gain real control over component configuration without touching theme templates.
Components are the contract
At the centre of this transformation is Single Directory Components (SDC). Each component declares its props and slots in a schema, and that schema becomes the contract the canvas uses to render editing controls. A minimal component definition looks like this:
# components/hero/hero.component.yml
name: Hero
status: stable
props:
type: object
required: [heading]
properties:
heading:
type: string
title: Heading
variant:
type: string
title: Variant
enum: [light, dark]
default: dark
slots:
actions:
title: Call to action buttons
Dynamic prop mapping and UI standardisation
Because components declare typed props, engineers can map them to entity field data rather than hard-coded values. A hero heading can be bound to a node title, a teaser image to a media field, and a badge to a taxonomy term. This isolates back-end structural definitions from front-end styling, so developers can package atomic components independently and editors can reuse them anywhere.
- Strict schemas prevent editors from producing layouts that break the design system.
- Enums and defaults become dropdowns and sensible starting points in the editing UI.
- Slots allow controlled composition, such as nesting buttons inside a hero.
Governance at scale
By enforcing clear validation schemas, layouts maintain a consistent visual identity and metadata compliance on high-traffic sites such as regional university portals and corporate intranets alike. Design-system changes ship once, in the component, and propagate everywhere the component is used.
Adoption tips for enterprise teams
- Start by converting your most-used blocks into SDC components with complete schemas.
- Keep prop names business-friendly; they surface directly in the editor UI.
- Version components and document allowed combinations of slots.
- Pilot the visual builder on landing pages before rolling it out to structured content.
Want help introducing component-driven page building on your platform? See our Drupal development services.