The secret: use SCSS or LESS to pack the combined effect of "p-3 border-1 shadow-sm rounded-2" into a single class.
Sooooo mixins? You can do that with Bootstrap as well.
I agree, but that approach seems to be uncommon or at least discouraged by the Tailwind creator.
I'd actually recommend Tailwind shops use the DaisyUI plugin which gives component classes similar to Bootstrap.
Indeed, the reasoning I've read falls close to the last paragraph of your previous comment. Components will consistently apply "atomic styles" everywhere and so are thought to be a replacement for "semantic styling" (sprinkling in some quotes because I don't know the exact terminology).
Yeah it's one of those things I just don't agree with them from practical experience. No beef against utility classes in general just not for everything. In fact I really like Bootstrap's which are just enough to help, but are still themeable: https://getbootstrap.com/docs/5.3/utilities/api/
Re:Thank You Bootstrap 1
by WorldMaker on Monday February 10, 2025 @11:27AM
(#43002066)
That just reinvents CSS the long way around. If you are making classes anyway, what do you need the shorthand DSL for the existing, robust DSL for?
You're not missing anything, companies like mine have done just this.
We supported a messy situation of 7 webapps using different technologies looking 7 different ways. Once we got them to use Bootstrap, was a cinch to consolidate to a single company brand.
The "big reskin" UX was gearing up for was as simple as a new theme, and was done without any drama. They were almost disappointed it was so easy, ha.
I like Tailwind, but it's a rotten fit for reskinning (not just changing font or colors). I'd much rather have a single .card class, vs "p-3 border-1 shadow-sm rounded-2" or whatever. Not all of us have have the luxury of a single modern app all using the same React components.