4 ms·

I used Tailwind for a year at work, never having used it before. I found it overrated, frankly, and not much of an efficiency boost. We had a "don't use inline

I used Tailwind for a year at work, never having used it before. I found it overrated, frankly, and not much of an efficiency boost. We had a "don't use inline styling or your own CSS classes if a Tailwind class already exists" rule. While the reasoning was understandable, it meant that every time I wanted to style or position a component, I had to browse the Tailwind docs to make sure I wasn't duplicating something. And Tailwind docs... let's just say they leave a lot to be desired.

tgv 4y ago
In your case, you'd be better of grepping tailwind's source. You could even spend some time writing a shell script that turns your proposed style rule into a regexp and runs it wherever tailwind's css file is.
agloeregrets 4y ago
We found that the tailwind VScode plugin was hyper helpful along with cutting down the unneeded in tailwind.config. Once you do that, most styling and positioning is variations on sizing, colors, and text sizes. Then the intellisense is pretty helpful to fill in the rest, some gotchas of course. `leading-` is an awful name for line spacing lol. A hardcore knowledge of CSS and all the governance you would use in vanilla is required to use tailwind however. It is important to see it from that angle. What seemed to help us (and I don't condone this for everyone, it just worked for us) was to go more extreme: No CSS without a bulletproof defense in a PR. The only exception we needed to break in our large scale platform was to style an SVG progress indicator with complex gradients. Angular's behavior around [ngClass] not just adding classes but removing them also was a bit tricky. Personally the behavior in whole feels like a bug but I know it isn't.