Every new Drupal project starts with the same debate: how will editors build pages? Paragraphs? Layout Builder? The new Display Builder? Drupal Canvas? Teams often feel they have to pick the “right” approach on day one and live with it for years, and editors end up learning a different editing model on every site.
Frontend Editing 2.0 takes a different approach. Editors work directly on the rendered page. Action links sit on the content itself, and the edit form opens in a sidebar next to the page, so editors never have to leave the frontend. The same experience works whatever builds the page underneath, because dedicated sub-modules handle Paragraphs, core Layout Builder and Display Builder. These builders rebuild the render array in ways a plain render-array scan can’t follow.
In this session we’ll look at what changed in the 2.x branch and demo it live: editing in place in a sidebar that can be widened or detached into its own window adding, moving, duplicating and deleting reference items without opening the parent form, with a separate permission for each operation live preview of unsaved changes, plus an experimental save queue that collects several edits and saves them at once (both use All Entity Preview) htmx-based AJAX on Drupal 11.3+, with automatic fallback to classic Drupal AJAX a configurable default state, status messages and many usability fixes.
We’ll then switch the same site between page-building approaches and show that the editor experience stays consistent. The page builder becomes an implementation detail you can change later, not a decision you have to get right on day one. Finally, for developers, we’ll look under the hood at the events, services and rendering pipelines you can use to integrate Frontend Editing with your own builder.
Learning objectives
Understand what is new in Frontend Editing 2.x and how to upgrade from 1.x.
Learn how to set up Frontend Editing for Paragraphs, Layout Builder and Display Builder, and see where Canvas fits in.
Use live preview, the save queue, duplication and fine-grained permissions to improve the editorial workflow.
Make a calmer, reversible choice about page-building strategy on new projects.
Speaker
Artem Dmitriiev