I was interested to find out what the differences were between Grunt-Sass and Grunt-Contrib-Sass.
Following on from my previous blog post on “Using Yeoman in your workflow“, it was brought to my attention during the Yeoman install when the interactive prompt asked if I wanted to use Libsass to compile Sass.
So I recently asked on Twitter and received the following tweets. Thanks to @sindresorhus for the explanation.
There are tonnes of web development tools to help front-end developers these days that it can start to become overwhelming. I know I was! (Not gonna lie!). So before we begin, I thought I would go through some of the steps of using Yeoman in my web development workflow.
First you’ll need to get a clear picture on what you’d like to achieve and what your end result will be. For me, I wanted to re-design an existing static website to make it responsive (more about RWD on a future blog post).
What is Grunt? Grunt is a JavaScript Task Runner.
As written on Grunt JS…
“Why use a task runner?
In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you’ve configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.”
Adeline Yaw 