72 lines
2.8 KiB
YAML
72 lines
2.8 KiB
YAML
uuid:
|
|
- value: 34be6fed-cd1a-4796-adb8-577340a359b4
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'You can do utility-first CSS with Sass'
|
|
created:
|
|
- value: '2024-07-09T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/07/09/you-can-do-utility-first-css-with-sass
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<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>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<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>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|