@cassidy the whole idea with using tailwind is using a component framework or library with it to encapsulate those long class names. Code like the one you share should only be the “output” of it all. It looks messy, but it’s a way of achieving a FP-like composition in CSS, and you can completely forget about !important, fighting specificity and so on. Customizing components is also a breeze using libs like tailwind-merge. You can also use `@apply`.

But yeah, the output can look ugly.

@cassidy data-barf=copious

@cassidy I've never used tailwind, but wow... What a mess! My eyes!

@cassidy Same!

I'd rather use the `style` attribute rather than inscrutable abbreviations mapping to the same CSS properties!