CSS or Cascading Style Sheet is one of the main mechanisms web pages use to add styling to the content. It allows us to change fonts, spacing, colours, sizing, layout and so much more. To learn more about CSS I suggest taking a look at W3 School. I really enjoy using CSS and seeing just how much it can be used to edit web pages from plain text to a content rich user experience.
The issue I found with CSS was the seemingly endless classes that an individual can create and unless you are following CSS naming conventions it can cause hours of trawling through the code to find issues.
I had always used normal CSS or a preprocessor such as Sass paired with a framework like Twitter’s Bootstrap or Google’s Material-UI. While they are more than viable solutions, I found that the pre-styling on the components left me fighting against stock styles with my own CSS.
This is why I decided to give Tailwind CSS a try, it meant that I would lose the pre-made utilities but unlock fast-to-use styling. I could create my own components and not have the hassle of reversing the pre-coded styling.
The main advantage to me is reduction of the use of a separate css file, Tailwind means that for a card element I can write simply write:
Which would output a styled card div with spacing from other elements, a dark gray background with contrasting white text and box shadow to make it have a 3d appearance. A similar div would require the code below:
From the above example you can see just how much time using tailwind could save you as well as forcing the user into a reusable naming convention. This is just scratching the surface of the power of Tailwind. It has a load of features that I utilise regularly such as Dark Mode, Variables, Animations and Tailwind also has a large active helpful community.
You might be thinking that all this customisation must come at the cost of file size, however they have paired up with PurgeCSS to remove this issue. At a very basic level it looks at all the classes you are using and removes the rest from the imported style sheets, meaning you only ship the used classes. All this is done very simply in Next.js by running ‘npm i postcss’ and creating a postcss.config.js file with:
That is all that is needed and it takes care of the rest. Since converting to tailwind I haven’t looked back and will soon be looking at updating Houghton Web Design to use the framework.
By Jordan Houghton
5th October 2021
Houghton Web Design © 2022