<p>Yesterday, I said that <a href="/daily/2024/07/08/back-to-sass-and-traditional-css">I'm working on a Sass project with no utility or atomic styles</a>.</p>
<p>But, the two aren't mutually exclusive.</p>
<p>You can do both.</p>
<p>You can write your own utility classes, like <code>flex</code>, <code>font-bold</code> or <code>text-red</code> in Sass or plain CSS.</p>
<p>You can use a framework like Tailwind CSS, but you don't need to.</p>
<p>In some projects, with existing stylesheets and usually other frameworks, you can't add anothe full framework without having unintended consequences.</p>
<p>Usually, if I want to introduce utility classes to an existing project, I start by writing my own that are inspired by a framework such as Tailwind CSS and maybe refactor to the framework later once the concept has been introduced and the codebase is able to work with it.</p>
<p>Yesterday, I said that <a href="/daily/2024/07/08/back-to-sass-and-traditional-css">I'm working on a Sass project with no utility or atomic styles</a>.</p>
<p>You can write your own utility classes, like <code>flex</code>, <code>font-bold</code> or <code>text-red</code> in Sass or plain CSS.</p>
<p>You can use a framework like Tailwind CSS, but you don't need to.</p>
<p>In some projects, with existing stylesheets and usually other frameworks, you can't add anothe full framework without having unintended consequences.</p>
<p>Usually, if I want to introduce utility classes to an existing project, I start by writing my own that are inspired by a framework such as Tailwind CSS and maybe refactor to the framework later once the concept has been introduced and the codebase is able to work with it.</p>