g4mbini → created an issue. See original summary → .
Let's stick to DaisyUI docs and the specs written by @pdureau !
All new components or variations that are not documented or come from other libraries should be implemented as custom development in a subtheme.
g4mbini → created an issue. See original summary → .
With UI Suite modules you have the ability to connect data and design directly in the UI, so only config threw manage display, layout builder, views, block layout, ...
When it's not possible (10-20% of the time) to "site build" you can use UI Patterns in code with twig include function or in php with drupal_render function.
You could also have a look at our last presentation of UI Patterns 2 @Drupalcon Barcelona for better understanding of the approach (regarding Components) --> https://www.youtube.com/watch?v=75wRtmpczOM&list=PLtGBRax0Lj4TXurFMpnd-y...
What do you think of using a new generation theming approach with UI Suite Initiative (that is leveraging SDC and new Icon framework) ?
Many themes are already available like :
- UI Suite Bootstrap
- or UI Suite DaisyUI
We could support the use of our ecosystem and also be available for a discovery meeting !
Don't hesitate to contact us. We are available on slack at #ui-suite-initiative ;)
Countdown is launched !!! TailwindCSS 4 is out there and DaisyUI 5 will be released in 37 days.
We will then create a new 5.0.0 branch !