Add daily email for 2024-07-09
You can do utility-first CSS with Sass
This commit is contained in:
parent
bab3f84031
commit
bc509aec2c
29
source/_daily_emails/2024-07-09.md
Normal file
29
source/_daily_emails/2024-07-09.md
Normal file
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
title: You can do utility-first CSS with Sass
|
||||
date: 2024-07-09
|
||||
permalink: daily/2024/07/09/you-can-do-utility-first-css-with-sass
|
||||
tags:
|
||||
- software-development
|
||||
- css
|
||||
- tailwind-css
|
||||
- sass
|
||||
cta: ~
|
||||
snippet: |
|
||||
You can do utility-first CSS with Sass, if you want.
|
||||
---
|
||||
|
||||
Yesterday, I said that [I'm working on a Sass project with no utility or atomic styles][0].
|
||||
|
||||
But, the two aren't mutually exclusive.
|
||||
|
||||
You can do both.
|
||||
|
||||
You can write your own utility classes, like `flex`, `font-bold` or `text-red` in Sass or plain CSS.
|
||||
|
||||
You can use a framework like Tailwind CSS, but you don't need to.
|
||||
|
||||
In some projects, with existing stylesheets and usually other frameworks, you can't add anothe full framework without having unintended consequences.
|
||||
|
||||
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.
|
||||
|
||||
[0]: {{site.url}}/daily/2024/07/08/back-to-sass-and-traditional-css
|
Loading…
Reference in a new issue