When I wrote my last post one year and one day ago , “vibe coding” was new. In fact, I heard about it for the first time while walking to some DrupalCon Atlanta social event — Bálint and Lauri were talking about it after a long conference day. By the end of 2025, it was in the dictionary. Three months into 2026 and it’s everywhere — for better or worse. 1 Also at the end of 2025, Bálint did a very…
I’ll be at DrupalCon Atlanta, where my primary goal is to connect and talk to all of you in the Drupal community who have questions about Experience Builder: hopes, concerns, aspirations, ideas, insights, anything! I won’t be talking at DrupalCon this time, but: I’m confident my team mate Bálint “balintbrews” Kléri will blow your mind in his technical session ! 🤓 Next, Lauri will talk about it…
It’s been a while since there was a screenshotless for Experience Builder ( XB ) week overview, but this is one of those. Solely adding more infrastructure and evolving existing ones. You may recall that last week , a “Publish” button was introduced that was supposed to be short-lived. It’s still around, but the server-side support for the intended UX did land this week: Ted “tedbow” Bowman and…
It’s hard to imagine, but … until now, Experience Builder’s ( XB ) live preview of the component tree (not to be confused with XB ’s chrome-free preview mode ) the content creator is assembling has been very imperfect. This week Dave “longwave” Long , Ben “bnjmnm” Mullins , Jesse Baker , Felix “f.mazeikis” Mazeikis , Lauri “lauriii” Timmanee , Bálint “balintbrews” Kléri and I made it just slightly…
Experience Builder ( XB ) most prominent UI piece is its preview canvas , where multiple viewport widths are visible next to each other. The preview canvas is meant for placing components, modifying their inputs and moving them around. For that reason, you cannot interact with the contents of each component. What if you do want to try that ? That’s where the new Preview functionality comes in that…
One of the most frequently performed actions in Experience Builder ( XB ) is inserting a component. That UI was moved to the sidebar last week to make it immediately available. After dragging a component onto the canvas, the most common next action is modifying the default component inputs . So that’s precisely what Jesse Baker , Harumi “hooroomoo” Jang , Luhur Abdi “el7cosmos” Rizal and Lauri…
A strong start of the week by Harumi “hooroomoo” Jang and Jesse Baker , to remove the “insert” panel appearing over the left sidebar, in favor of the components being listed inside the left sidebar: Experience Builder’s ( XB ) component library now appears in the left sidebar — making them easier to reach. ( Previously , there was a blue “plus” button that triggered a popover covering the left…
This was a with few user-facing changes in Experience Builder ( XB ). But some of the invisible changes are crucial for XB ’s future though. The biggest user-facing change of the week: Jesse Baker , Harumi “hooroomoo” Jang , Ben “bnjmnm” Mullins , hemanshu_412 and utkarsh_33 landed copy/paste support for individual component instances — and entire (sub)trees, of course! That’s ⌘ + C / ⌘ + V on…
Last week was quiet on the front end. This week there’s two big leaps forward! Leap #1 Experience Builder’s ( XB ) right sidebar has two tabs: “Settings” (for the per-component “settings”), which for Single Directory Components ( SDC s) shows a form to populate its props “Page data”, intended to allow modifying the the page you’re looking at if it’s a content entity. In other words: it should show…
Bálint “balintbrews” Kléri and Jesse Baker fixed a funny bug : the component inputs form was unscrollable , which meant that using Experience Builder ( XB ) in small viewports (or with complex components that have many inputs), you just couldn’t reach them 😅🙈 Dave “longwave” Long and I simplified the way XB represents Component config entity IDs, a small next step towards supporting multiple…