An Unexpected Benefit of Tailwind CSS

CSS has been around for a long time now. I have been using it for over a decade. In that time, we went from keeping it as a single separate file to using naming conventions and pre-processors. Moving past Atomic, BEM, and SMACSS, we started to put the CSS directly into the JavaScript. And to be honest, it has slowed down development for me.
So when I built earlier in the year, with the goal of building it in a single day, I choose to use Tailwind CSS as an experiment. It felt like moving back in time in a lot of ways, and I was really drawn to the approach of composing classes in HTML. Basically, never having used it before, it felt simple and easy to grasp. And it got out of my way to let me build quickly.
For those not familiar, Tailwind CSS is a utility-first framework that really tries to focus on giving you the building blocks to craft what you need. I am very much against CSS frameworks because of the opinionated styles. But Tailwind CSS is different, it’s just basic properties with some well-defined defaults. Anything I didn’t like, I replaced.

The Easiest Refactor Ever

Due to a project at work, I decided to migrate my personal blog I had just launched from Vue to Svelte. It was an experiment to ensure the technology choice was a wise one. I ended up liking the outcome and merging the branch into the master branch at the beginning of October.
The refactor took a lot longer than expected, but not because of Svelte or Vue. It was replacing the functionality I was getting from Gridsome that really cost me time. I had to replace the GraphQL file system interface to processing the markdown files. I also had to write custom code to handle the RSS feed and sitemap generation.
The only part that was not hard, was the styling. The act of actually migrating the HTML and Styles from Vue to Svelte.

Refactoring a Component

Vue uses a template structure that is basically HTML with some custom templates. Here is my Hero tile on the homepage of I choose a simple presentation component on purpose.
Here is the same component in Svelte.
It is really difficult to notice the difference. Basically the <template> tag needed to be removed, and the Gridsome specific <g-image> tag needed to be replaced with a plain old HTML compliant <img> tag.

The Benefits of Utility-first frameworks

At first glance, this may seem like a silly example. But that is the beautify. For every line template code that I migrated over, I only brought with it the CSS I used.
Another way to look at this — during the redesign I made a few decisions, like removing the search interface. Those components were not brought over, and the CSS was not included automatically.
Yes, you can get some of those benefits from CSS in JS or having component-specific CSS files. But I did not have to change any tooling. And if I removed part of a component, the CSS for that piece is gone as well.
Utility-first frameworks like Tailwind CSS, are an elegant and simple solution to solving the issues we all face when refactoring or removing dead HTML. How do we ensure the CSS is also correctly removed?