Feature request: unstyled components should act more like a "headless UI" #2099
Replies: 1 comment 1 reply
-
Headless UI only provides the JS functionality (with examples using Tailwind CSS utility classes optionally) daisyUI's unstyled config on the other hand is trying to provide the "structure" styles without "design decision" styles. So it would be possible to use it as a base for your own custom design system. In some components, honestly it's hard to draw a line where the structure ends and where the design decision starts but of course I'm willing to fix the issues and improve them as much as possible. For the toggle, what is your expectations for an unstyled version? |
Beta Was this translation helpful? Give feedback.
-
Hey @saadeghi,
First off - great library! Been using it very extensively in my work. I'm basically using DaisyUI as the building blocks to build my own design system and have overwritten nearly all of the built-in styles that come with it. I'd like to switch over to full "unstyled mode", but I noticed that unstyling some of the components completely removes their usefulness, so-to-speak. A good example of this is the toggle component. Removing the styling effectively just turns it into a checkbox, and the styles that make it appear as a toggle are too complex for me to just copy them into my codebase by hand.
I think it could be superbly helpful to expand the base styles of unstyled components so they act as the most basic form of themselves, similar to a headless UI library, as opposed to just removing all of the CSS. This would make it easier for devs to build design systems on top of Daisy without having to import unnecessary theme CSS that would just end up being overwritten anyway.
Beta Was this translation helpful? Give feedback.
All reactions