|
|
|
|
|
|
by e12e
1380 days ago
|
|
|
> Suddenly you are juggling 9 classes that also have some fixed value In my experience, devs using tailwind will happily wait until there are 20+ classes before refactoring - on the surface this seems insane - but if all you're editing is single, re-usable components (eg: "text on a page" is in a custom "article" component) - it's no longer quite as crazy. > Theming is OK to some point (like making dark version) but if you need to make broader changes between multiple themes it just crumbles. You wouldn't make css zen garden with tailwind - you would make such sweeping themes at component level, where you can change style, behavior (js) and markup all together. Again - tailwind isn't for document styling, but for building applications - that happen to feature html and css as implementation details. |
|
|
And yet it's app developers i know that hate it and don't want to use it (they already have single file components). But agencies making super custom content websites seem to be all over it. https://www.awwwards.com/websites/tailwind/ These websites are css zen gardens if anything.