Reusable Content in Drupal Canvas: What Works Today and What Editors Still Need

Room Romulus Time Slot Fri 11:30am to 11:55am (11/27/26)

Drupal Canvas gives Content Editors a flexible way to build pages. But what happens when the same content should appear on several Canvas pages? 

I tested three existing approaches with Drupal 11.4.10 and Canvas 1.12.0:

  • Canvas Pattern Components
  • Canvas Pattern Blocks
  • Canvas Entity Reference with reusable Block Content

For all three approaches, I used the same example: one central promo item placed on two Canvas pages.
The technical reuse already works: create once, use on several pages, edit centrally, and all pages update.
The bigger difference is the editor experience. 

When an editor selects shared content, they should quickly understand:

  • Is this content shared?
  • Where else is it used?
  • What happens if I change it?
  • Where can I edit the original source?

To explore this, I built a small proof of concept based on the Entity Reference approach. It shows that the content is shared, the source title, usage information, a warning before global changes, and permission-aware actions for Edit source and View usages.

Both actions open in a right-side drawer so the editor stays inside Canvas. The shared source can be edited and saved there. After saving, the Canvas preview updates automatically and the editor returns to the normal Shared content inspector with the same component still selected.

The session will compare the three approaches, demonstrate the PoC, and discuss how reusable content could become clearer and safer for Content Editors.

One open question is “Make local copy” turning one shared placement into independent local content. This sounds simple for editors, but technically depends on how the reusable component stores its data.

Learning objectives 

After this session, attendees should be able to: 

  • Understand three current ways to reuse content in Drupal Canvas. 
  • Understand the difference between patterns, blocks and entity references.
  • Understand the difference between copied content and centrally managed content. 
  • Consider permissions, revisions and editor experience when choosing an approach. 
  • Recognize current UX gaps around shared content in Canvas. 
  • See one possible approach for improving the editor workflow.
Speaker
Hanan Alasari