TailwindCSS is an awesome utility-first CSS library for creating beautiful layouts with less customized CSS.

There’s a good chance you’ve heard about Tailwind. But, have you tried using it?

In this article, I’ll share the things that make Tailwind different from other component libraries I know. And I’ll discuss why you should start using it.

Note that everything here is my opinion. I’m not saying I’ve used all the component libraries in the world, lol.

Before TailwindCSS

…there were component libraries like Bootstrap and Material UI, to name a few. These libraries come with a set of pre-defined components. For instance, the most common (or heard of) is probably PrimaryButton.

These libraries reduce the hassle of designing elements from scratch with CSS. Most of these libraries also do an amazing job of making the components customizable by the user, so that they do not have to stick to the creator’s decisions.

However, this customizability most of the time involves overwriting. For example, creating new classes to overwrite the existing styles provided by the library.

This is not a big issue per se (depending on the user, for me it is), but you still have to go with the “Do I like the way this is styled? No. Let me overwrite it” kind of flow.

Some developers may see these already made components as just what they need. But creators cannot always make something perfect for every user. Thankfully, as stated earlier, they do a great job of making the components customizable.

#tailwindcss #css #web-development #developer