Preface

Conventions Used

Code Samples

Code in this book is displayed using a fixed-width font, like so:

A Perfect Summer's Day

It was a lovely day for a walk in the park.

The birds were singing and the kids were all back at school.

You’ll notice that we’ve used certain layout styles throughout this book to signify different types of information. Look out for the following items.

Tips, Notes, and Warnings

Hey, You!

Tips provide helpful little pointers.

Ahem, Excuse Me ...

Notes are useful asides that are related—but not critical—to the topic at hand. Think of them as extra tidbits of information.

Make Sure You Always ...

... pay attention to these important points.

Watch Out!

Warnings highlight any gotchas that are likely to trip you up along the way.

Supplementary Materials

https://www.sitepoint.com/community/ are SitePoint’s forums, for help on any tricky problems.

[email protected] is our email address, should you need to contact us to report a problem, or for any other reason.

Getting Started with Tailwind CSS

There are two main types of CSS framework. One is based around components—a group that includes frameworks such as Bootstrap, Foundation, and Bulma. The other type of CSS framework is based around utilities—a group that includes the likes of Tachyons, Tailwind CSS, and Windi CSS.

Component vs Utility Classes

If you’re not clear on the difference between component and utility classes, jump to the What Is a Utility Class? section below, and then continue reading from here.

For many years, component-based frameworks were the de facto standard for building websites quickly and easily. But all this magic comes with a price. Without serious customization, sites built with such frameworks look similar to each other. And customization is a real pain in the neck for anyone who wants to build something more complex and/or creative. Component-based styles are easy to implement, but inflexible and confined to certain boundaries. Solving specificity issues while trying to override the default styles of a particular framework isn’t a fun and productive job.

Utility-first frameworks were created to solve this problem. A utility-first framework is built with low-level functionality in mind. Utility classes offer much more power and flexibility than component classes.

Utility-first frameworks provide the following advantages:

Utility classes operate at a low level. This means we have more control and flexibility over how we apply them—a concept that’s similar to the power and flexibility offered by a low-level language like C or C++, in contrast to high-level languages such as JavaScript or PHP.

Utility classes are easy to customize, so we can build any design.

A utility-first approach scales well. It’s great for managing and maintaining large projects, because we only have to maintain HTML files, instead of a large CSS codebase. It’s already used with success by big sites like GitHub, Heroku, Kickstarter, Twitch, and Segment.

Utility classes can be adopted to any design.

Utility classes are completely customizable and extensible. It’s easier to build unique, custom website designs without fighting with unwanted styles.

Utility classes allow for much easier implementation of responsive design patterns.

Utility classes have consistent styles, which gives us a ready-to-use design system. We can also create our own design system if we need to.

With utility classes, we can still extract common, repetitive patterns into custom, reusable components. But in contrast to predefined components, custom components will be exactly what we need.

In summary, we can say that a utility-first framework gives us balance between the concrete and the abstract.

Now that we’ve seen how useful utility-first frameworks can be, it’s time to pick one and see what it can do for us in action. In this book, we’ll explore Tailwind CSS, which is the most popular of the utility-first frameworks.

What Is Tailwind?

Tailwind is a set of low-level, reusable utility classes that can be used like building blocks to create virtually any design we can imagine. This utility-first framework covers the most important CSS properties, but it can be easily extended in a variety of ways. It can be used either for rapid prototyping or for creating full-blown designs.

Tailwind has great documentation, covering every class utility in detail and showing the ways it can be customized. There’s also a playground where you can try out your ideas. You can also check out Tailwind’s screencasts if you prefer to learn by watching.

As of version 2.0, Tailwind CSS supports the latest stable versions of Chrome, Firefox, Edge, and Safari. There’s no support for any version of IE, including IE11.

What Is a Utility Class?

As we already know, Tailwind’s main characteristic is the use of utility classes. But what is a utility class?

While a component class is a collection of predefined CSS settings applied in an opinionated fashion, a utility class is mostly a single CSS property or behavior that we can use freely in a predictable way. This gives us the freedom to combine, mix and match different settings depending on our requirements. We have greater control over each element’s appearance. We can change and fine-tune an element’s appearance much more effortlessly with utility classes.

In Bootstrap, we create a button by using predefined component classes, as in the following example:

btn btn-success>Success

Here, the btn and btn-success are the so-called component classes. Each one of them represents a collection of predefined CSS settings.

In Tailwind, we create a button by using utility