The transition from Drupal's native Layout Builder to Display Builder at UI Suite is a carefully planned process. We are following a phased migration strategy, starting with our "Article" and "News" entity view displays.
A major advantage, as outlined in the migration-from-layout-builder.md documentation, is the ability to have both systems active on the same display. This allows our team to test and validate the Display Builder version without impacting the live site.
The migration process itself is remarkably smooth. When Display Builder is activated on a display that already uses Layout Builder, it automatically triggers a migration that converts Layout Builder's sections and components into a Display Builder-compatible structure.
Each migration is logged as a step in the history, allowing us to undo and redo changes with confidence. This provides a safety net that has been invaluable during our testing phase.
However, the migration is not entirely automatic. As the documentation points out, Display Builder's rendering approach bypasses templates like block.html.twig for performance gains.
This means any custom logic in our preprocess hooks for blocks needs to be refactored, typically by moving it into the components themselves. Acknowledging this upfront has allowed us to plan the necessary development work and ensure a successful transition.
Powered by Drupal and Display Builder
Design System native by UI Suite Team
This template is very lightweight. It is perfect for ensuring an optimal score on performance tools, especially when combined with a proper Drupal cache configuration.
Reply