I use daisyUI for my side project and it is fantastic! Many thanks to the creator for their hard work.
My Journey to build daisyUI: Why Tailwind CSS was not enough?
11–18 of 18 posts
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#12I’m not surprised tailwind was not enough. If you use tailwind you’ve decided css or scss was not enough, meaning probably nothing will ever be enough for you.
Those unable to walk will always trade in their crutches for wheelchairs.
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#13I’m not surprised tailwind was not enough. If you use tailwind you’ve decided css or scss was not enough, meaning probably nothing will ever be enough for you. Those unable to walk will always trade in their crutches for wheelchairs.
> If you use tailwind you’ve decided css or scss was not enough, meaning probably nothing will ever be enough for you.
That's not true at all. I have been one of the earliest adopters of Tailwind and it is 100% enough for me and has been for 5 years.
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#14I’m not surprised tailwind was not enough. If you use tailwind you’ve decided css or scss was not enough, meaning probably nothing will ever be enough for you. Those unable to walk will always trade in their crutches for wheelchairs.
CSS is genuinely an awful layout system.
I could rant, but I'll just link Casey Muratori's take on CSS instead. https://feeds.resonaterecordings.com/software-unscripted
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#15Hello, thank you for this. I recently got PR(s) to add astro/tailwind/daisyui to yakshalang.github.io from 2 devs. I'm blown away from how good the website looks now. :) Happily deleted my homegrown and badly written CSS.
I love seeing open source success stories like this. Not only did someone take the time to refactor the website and make a very exhaustive PR (https://github.com/YakshaLang/yakshalang.github.io/pull/4), you as the maintainer showed a willingness to scrap your own work (project maintainers are sometimes too reluctant to discard significant original work of theirs)
I'm curious if this was all done on github, or if you and the PR submitter discussed the cleanup via other channels before they just blazed ahead with the refactor
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#16If I remember right, the design philosophy around why Tailwind encourages you to write all the different classes out individually each time is that it wants you to reuse components rather than CSS classes because as the codebase scales and gets more complex you now know that any changes are only going to affect that component and not that component + whatever dev decided to use that custom class you made somewhere el…
We’re moving to Tailwind in a project rearchitecture initiative next year and I’m _thrilled_. We have SASS files, and a lot of them. They are mostly well-organized (ish) and, at one point, they were well-maintained.
But, this component needs a little more padding here and not there. We need flexbox - which parts? Some. Some here, some there, but not all of it…yet. What about grids? Sure, maybe, how? Media queries spread all over the place wrapping things arbitrarily. Oh! And scoped styles every which way for that component-specific flair!
Our component class declarations are about to get a lot more verbose, and I’m all for it. I’d much rather see that, and know what the visual structure should be, instead of tracing a class back through mountains of tacked-on SCSS to add a child class that gets applied in one place that makes a thing have zero margin.
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#17unocss!
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#18Hello, thank you for this. I recently got PR(s) to add astro/tailwind/daisyui to yakshalang.github.io from 2 devs. I'm blown away from how good the website looks now. :) Happily deleted my homegrown and badly written CSS.
I love seeing open source success stories like this. Not only did someone take the time to refactor the website and make a very exhaustive PR ( https://github.com/YakshaLang/yakshalang.github.io/pull/4 ), you as the maintainer showed a willingness to scrap your own work (project maintainers are sometimes too reluctant to discard significant original work of theirs) I'm curious if this was all done on github, or if yo…
We discussed this on discord :)