You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
It makes the html classes look so much less messy, since it will have most of the essential styles defined under small class names (e.g. btn or modal) and a couple modifiers (e.g. btn-accent or modal-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.
I also really like how DaisyUI uses native html elements wherever is makes sense, such as using a <dialog> element for its modal component, which again gets its basic styling with just a simple modal 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. 😇
I will agree with this.
I mean you can use bits-ui with Daisy-ui no problem {i do all the time), but shadcn will break daisy-ui. So this Discussion is probably more suited to the shadcn-svelte repo.
That being said...
Obviously Daisy-ui tries to provide some of the same solutions as shadcn with a css only approach, but this doesn't have all of the great accessibility, state management and composed components that comes out of the box with shadcn.
I mean after all shadcn is styled with opinions about how to do it, maybe there can be an option to use use daisy instead of the shadcn styles to make that library as flexable as possible.
@Evertt
You can always just install bits-ui and copy paste from shadcn. You will propbably have to just change all the styles to use bits-ui stuff but it works fine for the most part.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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