Would you see any benefits / added value to adopting some of DaisyUI's approach? #569
Replies: 1 comment
-
I will agree with this. @Evertt |
Beta Was this translation helpful? Give feedback.
-
I will agree with this. @Evertt |
Beta Was this translation helpful? Give feedback.
-
This question is actually both for bits-ui as well as shadcn-svelte.
There's a few things I really like about DaisyUI's way of doing things:
btn
ormodal
) and a couple modifiers (e.g.btn-accent
ormodal-open
), etc. And then still you can add more TailwindCSS classes after that, to add / override styles if you'd like. But in any case, in the end, your html classes won't look nearly as messy as they often do with only TailwindCSS classes.<dialog>
element for itsmodal
component, which again gets its basic styling with just a simplemodal
class.So yeah, I really like the readability and simplicity of it. But I also love the flexibility and "completeness" of bits-ui, meaning how it takes care of all the a11y features for us etc.
So I just wonder if there could be kind of this perfect world where some of DaisyUI's ways of doing things could make its way into bits-ui and / or shadcn-svelte, without losing any of the wonderful features that bits-ui and shadcn-svelte offer us. 😇
Beta Was this translation helpful? Give feedback.
All reactions