Move daily emails into the blog page
This commit is contained in:
parent
be69398931
commit
1b8441608f
828 changed files with 9 additions and 196 deletions
26
source/_posts/2024-07-11.md
Normal file
26
source/_posts/2024-07-11.md
Normal file
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: How I started using utility-first CSS
|
||||
date: 2024-07-11
|
||||
permalink: daily/2024/07/11/how-i-started-using-utility-first-css
|
||||
tags:
|
||||
- software-development
|
||||
- css
|
||||
- tailwind-css
|
||||
cta: ~
|
||||
snippet: |
|
||||
How did I start using atomic classes and utility-first CSS?
|
||||
---
|
||||
|
||||
Before I started using atomic CSS classes, I used to use a popular component-based CSS framework.
|
||||
|
||||
You'd include the styles as well as the HTML markup you needed.
|
||||
|
||||
Whilst using the other framework, I started to sprinkle CSS classes on top of my existing styles, to make it easy to set values such as text sizes, colours, margin and padding without repeating myself and duplicating styles.
|
||||
|
||||
Later, I realised I didn't need the original framework and I could do it myself with atomic classes.
|
||||
|
||||
Page by page and component by component, I refactored everything to use atomic classes.
|
||||
|
||||
Once everything was refactored, I removed the original framework.
|
||||
|
||||
I haven't looked back.
|
Loading…
Add table
Add a link
Reference in a new issue