Add daily email for 2024-03-15
Everything is a trade-off
This commit is contained in:
parent
7930dc38a6
commit
8f0222be76
24
source/_daily_emails/2024-03-15.md
Normal file
24
source/_daily_emails/2024-03-15.md
Normal file
|
@ -0,0 +1,24 @@
|
|||
---
|
||||
title: Everything is a trade-off
|
||||
date: 2024-03-15
|
||||
permalink: archive/2024/03/15/everything-is-a-trade-off
|
||||
tags:
|
||||
- software-development
|
||||
cta: d7eol
|
||||
snippet: |
|
||||
All solutions have advantages and disadvantages. Which works best for you?
|
||||
---
|
||||
|
||||
I recently added a custom `wrapper` class within a Tailwind CSS project.
|
||||
|
||||
It combined the `max-w-6xl`, `mx-auto` and `px-4` classes using `@apply`, which I rarely use.
|
||||
|
||||
I added it so we didn't have to add the same classes multiple times.
|
||||
|
||||
The advantage was it removed some duplication, but people needed to switch from the Twig template to the CSS file to remember what the `wrapper` class did.
|
||||
|
||||
This undoes some of the advantages of Tailwind CSS and utility classes - the ability to stay in one file without needing to context switching, and easily reading what classes are on an element and immediately knowing what styles are applied to it.
|
||||
|
||||
Everything is a trade-off.
|
||||
|
||||
You need to decide which option feels right for you.
|
Loading…
Reference in a new issue