Laptop open on desk with code on screen.
Photo by Safar Safarov on Unsplash

If you’ve been following along, you know I’m a huge fan of Tailwind CSS. And a pretty early adopter. I’ve documented my first week (v0.1.4) and my first year (v0.6) with it.

This week Tailwind 2.0 comes out and I just thought I’d give an update on where I stand with it.

I still love it.

I’ve been using it for each project I’ve done since it’s release in 2017. I haven’t touched another framework or written my own CSS (outside of a few custom bits here and there within Tailwind) and it’s been great. I’ve worked on small projects alone and very large projects with a team.

Old Code Smell

Opening an older Tailwind site and I know what everything is without having to think. Also, I can scan the classes and get a pretty good picture of what it will look like without diving into ancient dusty CSS files.

Black and white photo of a man standing in front of a truck.
This image has nothing to do with the article. I just thought it was cool. Photo by NOAA on Unsplash

Team Player

And, of course, to keep things looking too similar, it’s very easy to extend the config file and change up the site colors. Helpful for one of our apps which serves multiple templated domains.

Tailwind UI

How will Tailwind shape things moving forward? I honestly don’t know, but for someone who was been writing CSS since the 20th century, it’s really great to simply not think about anymore.

More of Me

Making stuff up since 1977

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store