Tailwind CSS v1.0 - A utility-first CSS framework for building custom designs.

I've used Tailwind on every project I've worked on since I first tried it, it's really the perfect companion for any dev!

Pros:

Makes it really easier to bring to life any design you can imagine

Cons:

Makes going back to writing CSS painful

Move over Bootstrap, Tailwind is in town.

Pros:

The pre-built components are incredible!

Cons:

Can't think of any

whats new in this update?

I went all in on using Tailwind as the backbone of my companies UI Kit as soon as the Beta1 came out - I have had no regrets. As a Vue developer, it has really streamlined my processes while eliminating some "clutter classes" that I never used with Bootstrap. The classes are very readable and the use of Pseudo-classes are amazing. You will not be disappointed by making the switch over to Tailwind for your future projects.

Pros:

Easy to use, classes are common sense and closely aligned with some Bootstrap classes, and a nice clean slate for barebones projects.

Cons:

This is not a UI kit. This is not a 1:1 Bootstrap replacement. This can be a con, depending on who you are.

Tailwind is one of those things that at first glance you may be inclined to dismiss. Its inline approach is at first a little jarring--but stick with it. TW makes prototyping faster, maintaining easier, and just generally writing CSS less painful. However, PurgeCSS is a nearly a must and that is a TW weakspot. Getting PurgeCSS setup for anyone not familiar with configuring a dev pipeline is a TW speedbump. That said, that's also doable -- you just need to expend a little elbow grease. I'm not looking back -- TW is great.

I've been using it now for like a year and love how fast I can write CSS and style but still following a plan which is in my configuration file.

Pros:

It's fast, it's easy, it's still CSS and comes with a great configuration file. don't mistake it for normal inline styles. It is much more!

Cons:

It takes some time to FEEL the difference, you need to rethink your workflow

is it provide templets also?

I use Tailwind for all my new projects now, it's just so much easier to work with. Some people say that they prefer writing custom CSS, the thing is you can still do that without restrictions. Going back to older projects that aren't set up with Tailwind is kinda painful now.

Pros:

Speed, ease and consistency of new designs. Not tied to any specific style as some frameworks are

Cons:

People don't understand how good this is unless they give it a go.

Been using Tailwind in production since around 0.6 and it's clear that Adam has put a lot of thought into making the most flexible utility-first CSS Framework out there. It has a great balance between a lot of options and some great defaults in terms of colours and fonts, without providing you default-looking components that you'll find cropping up on every site using it in a few months like some other frameworks. Definitely check out some of the videos Adam posted on his YouTube channel where he duplicates existing web apps with just the out of the box utilities. Most importantly; don't hate on the idea of utility-first CSS until you give it a go. It's a powerful tool and there's no wonder places like GitHub and Algolia are leveraging the methodology.

Pros:

Really helps you rapidly build out pretty much any design with just utility classes. Rarely will you find yourself creating custom CSS

Cons:

You have to already know CSS pretty well to use it; the classes are wrappers over underlying CSS attributes.

I was very skeptical in using a utility framework because I didn’t like the idea of “styling in html”. But after on some unmaintainable projects due to massive CSS files, Tailwind has proven to be the perfect solution. Won’t work on projects without Tailwind anymore.

Pros:

Quick to learn. Easy to implement. Major speed increase in workflow.

Cons:

Can’t think of any.