I appreciated this bit of nuance from a post on Viget's blog: There could be a whole article written about the many flavours of Tailwind, but broadly

CSS-Tricks is a go-to destination for web designers and front-end developers seeking insights into CSS techniques, web design trends, and best practices. Through a rich collection of articles, tutorials, and code snippets, CSS-Tricks equips developers with the knowledge and tools needed to create visually stunning and user-friendly websites. Whether you're looking to master CSS layout techniques, explore responsive design principles, or stay updated with the latest CSS features and browser compatibility issues, CSS-Tricks offers practical guidance and inspiration for elevating your web design skills.

CSS-Tricks

The way you use some particular technologies can be super different from how someone else does, to the point they share little resemblance. I appreciated this bit of nuance from a post on Viget’s blog. There could be a whole article written about the many flavours of Tailwind, but broadly speaking those flavours are: 1. Stock tailwind, ie. no changes to the configuration, 2. Tailwind that heavily relies on @apply in CSS files but still follows BEM or some other component organization, 3. tailwind UI, and 4. heavily customizing Tailwind.

"Disambiguating Tailwind"

I really like this article’s point where they mentioned the following:
“When you multiply the fact that any given single technology can be used so many different ways with how many different technologies are in use on any given project, it’s no wonder why developer’s experience on projects is so wildly different and you hear a lot of people talking past each other in debate.”

That’s so true! We extend Tailwind and use mostly our custom classes