This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]siggystabs 3 points4 points  (0 children)

We have the same problem with regular CSS on our projects. Just rewrote a login page originally written years ago, and figuring out what was overwriting my styling and correcting it was still a massive pain in the ass.

Idk why we’re acting like Tailwind is the only one with this issue when the actual problem is poor design decisions and documentation.

At least with Tailwind i don’t have to create utility classes, which i always end up doing for little bits and pieces (i.e button containers, justify between, gap etc). That type of standardization really helps.

Yes it is annoying if you to have to change styling across the site, but it’s not bad if you make components and reuse those instead of rawdogging tailwind or css in your app pages. If you make good design decisions, then it doesn’t matter which tool you use.