Re:My Journey to build daisyUI: Why Tailwind CSS was not eno...
by pankajparashar on Friday December 22, 2023 @07:00AM
(#38733333)
If you want to deep dive more into this css methodology, you should check out this interview with ThierryK.
https://css-tricks.com/thierry-koblentz-atomic-css/
Re:My Journey to build daisyUI: Why Tailwind CSS was not eno...
by phatskat on Saturday December 23, 2023 @04:08AM
(#38742758)
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.
Edit: The core concepts section is worth a read in it's entirety but I believe this is the relative part:
https://tailwindcss.com/docs/reusing-styles#avoiding-prematu...