- Issue created by @pdureau
- π«π·France nod_ Lille
This will also allow themes to be much more reusable, making it possible to deploy a SDC-based theme configuration through a recipe
- π¦πΊAustralia pameeela
@pdureau thank you for this proposal! Just FYI, we are just one day away from a commit freeze for the RC release of Drupal CMS on Monday, and from there, we won't be able to add any major new features until after version 1 is released on Jan 15.
Right now, the leadership team and track leads are pretty focused on getting ready for this, as you might imagine! Happy for any discussion to occur in the meantime, just wanted to let you know, in case it is a bit quiet in here for a while :)
- π«π·France pdureau Paris
Thanks Pamela for the notice. I totally understand the situation. Let's focus on delivering the first releases of both Drupal CMS and UI Patterns 2, and let's talk again about possible synergies when possible.
- πΊπΈUnited States dalemoore
I would like to co-sign this request. I first started out trying to integrate components in our new flagship site a few months ago, and started using Single Directory Components for the job. I love this new addition to Drupal, but incorporating them into the site is painful. Having to create a new Twig template every single time you want to call values from a field, block, or whatever as an SDC is cumbersome to say the least. I was finding myself repeating the same Twig code over and over across content types, fields, etc., which Twig's extend capability is helpful with, but it means what's setup in the Drupal UI under Manage Display or in Layout Builder is no longer 1:1 with what's in the Twig template. It feels very "un-Drupal"-like working this way. We really need something like UI Patterns in Core to get the most out of their use. Experience Builder is many more months away and while it seems to be able to eventually control the entire layout of a site, not just the content area like Layout Builder, it remains to be seen if everyone would adopt it. And I imagine it will take many years for it to fully replace everything if that's the goal. Putting something like UI Patterns in Core will work for now. Just my 2Β’.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Note that the Experience Builder 1.0 is targeted for July.
- π«π·France pdureau Paris
Note that the Experience Builder 1.0 is targeted for July.
And UI Patterns 2 is targeted for next week π (February the 4th)
The 2 projects are not in competition, UI Patterns 2 is not a display builder like XB but a plugins provider for the current display builders (Block layout, Manage display, Layout Builder, Paragraph Layout, Views...).
6 months is a long time away, so it gives us time to help the SDC ecosystem to be compatible with display building and site builders to get use of the concepts. If you check the current state of SDC themes, most of them will not work well with display building because of missing variables, unknown variables, template logic issues, JSON schema mistakes... It will hurt Experience Builder(or any other new generation display builder) adoption.
So, I maintaining my proposal :)
- π¦πΊAustralia pameeela
Hey @pdureau thanks for coming back to this!
For my part, I don't really understand what it would look like to adopt this for Drupal CMS. I do realise that the two are not completely incompatible, but there are large parts of UI Patterns that would be somewhat obsolete with XB (in terms of providing plugins for other display builders like LB that won't be needed).
So given that as you say, it's not a display builder, what would this look like?
- π«π·France pdureau Paris
So given that as you say, it's not a display builder, what would this look like?
It provides SDC components for the existing display builders:
- Block Layout: as blocks
- Manage Display: as field formatters
- Layout Builder: as blocks, layouts and field formatters
- Views: as styles, rows and field formatters
So, it doesn't offer a brand new "experience". It just plugs SDC to the existing UI tools. That why I believe it will be a nice and softer transition from old school display building.
UI Patterns 2.0.0 was released yesterday by the way. Here is the documentation: https://project.pages.drupalcode.org/ui_patterns/