From e12635febb5609fddc90d481851f34a659297eb8 Mon Sep 17 00:00:00 2001 From: Stefan Imhoff Date: Wed, 4 Sep 2024 18:16:56 +0200 Subject: [PATCH] fix: typo --- src/content/journal/2014/gulp-tutorial-16-postcss.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/journal/2014/gulp-tutorial-16-postcss.mdx b/src/content/journal/2014/gulp-tutorial-16-postcss.mdx index 67308cb..566c2d4 100644 --- a/src/content/journal/2014/gulp-tutorial-16-postcss.mdx +++ b/src/content/journal/2014/gulp-tutorial-16-postcss.mdx @@ -15,7 +15,7 @@ This is the 16th part of my series _Introduction to Gulp.js_. Today, I will show I use Sass and SCSS now for a long time, started with _Compass_, moved to _Ruby Sass_ and wanted to move to _libSass_, but dependencies on my beloved Gems held me back. -There are numerous Preprocessors, Libraries, and Frameworks, which extend CSS. And a lot of them do good work and I didn’t want to miss variables, nesting, or mixins. But Ruby Sass and Compass in particular are **slooooooooow**because Ruby is slow. Compiling my website’s styles took 7-8 seconds, but I know of projects where one change will trigger a recompile, which takes **more than a minute**! +There are numerous Preprocessors, Libraries, and Frameworks, which extend CSS. And a lot of them do good work and I didn’t want to miss variables, nesting, or mixins. But Ruby Sass and Compass in particular are **slooooooooow** because Ruby is slow. Compiling my website’s styles took 7-8 seconds, but I know of projects where one change will trigger a recompile, which takes **more than a minute**! ## What is PostCSS, and why should I use it?