Problem/Motivation
Is this project an alternative approach to the Experience Builder project? Or is it something that may be combined with it? I'm just confused what's the primary purpose of it. Thanks for clarifying.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|
Comments
Comment #2
pdureau commentedHello mxh,
Thanks for your interest.
Like Experience Builder, this project is a next generation display building tool for Drupal. "Next gen" because both are:
See more: https://youtu.be/3OYXZ8-G4gk?t=1597
However, the 2 projects are different. Display Builder is currently targeting a wider horizontal scope (more display building coverage):
But Experience Builder is currently targeting a deeper vertical scope (before and after display building):
And they also differ by the technical and strategic choices. For example, Experience Builder is a complete ReactJS app, aside of Drupal, when Display Builder is just an usual Drupal module using HTMX.
So we are going in 2 different directions and our friendly competition will be only on the shared subset of our scopes. So, not such a big deal.
I hope both will be usable in a same project if this is needed by a team. Anyway, we are actively collaborating to provide same or compatible low level API and to improve Drupal Core together. So it is a win-win situation.
This is a display building tool made by a team specialized in design systems and display building since 2017: UI Suite people. This project is new, right, but it is only a thin layer upon APIs we are building for many years, and which are already used, tested and loved by many.
So, it is the natural next step for us. We are excited about what can be done here and we hope people will enjoy using this tool.
Is it clearer for you?
Comment #3
mxh commented@pdureau Thank you for providing this detailed answer, this makes it clear now. You've set it to postponed maybe for some good reason, for me it's fixed now since this has been clarified.
Comment #4
pdureau commentedSo, fixed :)
Comment #5
anybodyJust asked myself the same and found this. I guess it might be really useful to put this comparison on the project page?
XB will be widely used in the future, so I think people will look for exactly this comparison, when deciding for a solution.
Comment #6
vasikesorry to re-open this issue, but I totally agree with @anybody, so @pdureau, please update the project page with this very useful comparison
info.
and thanks a lot.
Comment #7
pdureau commentedOK :) I will provide at least a link to this issue, maybe a bit more.
By the way, this is from my Drupal Dev Days (Leuven 2025) slides:
Comment #8
pdureau commentedBoth projects have changed a lot in one year.
Updated information will be added in #3580549: Update documentation