DevHub: Compile sass using grunt

[atimmer]

Currently we compile using ruby sass, but it would be better to use grunt so we can use other things as well, such as autoprefixer and cssjanus.

This way it is easier to get started, using only 'npm install', 'grunt sass' and 'grunt watch'.

[Otto42]

I believe that you're posting these in the wrong place. This is the meta.trac, we talk about various bits and components of the WordPress.org website itself here. If you have any core enhancements, you should use the core.trac instead.

[atimmer]

These tickets are about devhub, so they belong here. I am planning to work on these and I am posting these here to have a place to put the patches.

[atimmer]

Because I cannot change the ticket, more clarification here about the ticket:

This ticket is about the developer.wordpress.org theme that is located here: https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer

Currently we compile using ruby sass, but it would be better to use grunt so we can use other things as well, such as autoprefixer and cssjanus.

[atimmer]

1014.diff just adds a package.json and a Gruntfile.js and recompiles the CSS.

[coffee2code]

In 3720:

developer.wordpress.org: Switch from ruby sass to Grunt and reprocess CSS files.

Props atimmer.
Fixes #1014.