From 23edad69b078a90bfce8ed436eb0a0b9ae824faf Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 29 May 2024 22:21:48 +0100 Subject: [PATCH] Add daily email for 2024-05-27 Why do you still write Sass? --- source/_daily_emails/2024-05-27.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 source/_daily_emails/2024-05-27.md diff --git a/source/_daily_emails/2024-05-27.md b/source/_daily_emails/2024-05-27.md new file mode 100644 index 00000000..971095f7 --- /dev/null +++ b/source/_daily_emails/2024-05-27.md @@ -0,0 +1,21 @@ +--- +title: Why do you still write Sass? +date: 2024-05-27 +permalink: daily/2024/05/27/why-do-you-still-write-sass +tags: + - software-development + - css +cta: ~ +snippet: | + If you still write Sass, why do you do it? +--- + +Yesterday, I asked [if it's time to stop writing Sass][0]. + +If you still use Sass and are writing new styles with Sass, I'd like to know why. + +Reply to this email and let me know. + +I'm working on a project and migrating from the existing Sass styles to Tailwind CSS-generated utility classes, but with CSS custom properties (variables) and other Sass-like features now supported by browsers, writing vanilla CSS again is an interesting option. + +[0]: {{site.url}}/daily/2024/05/26/is-it-time-to-stop-writing-sass