CSS build scripts

[justintadlock]

I'm fairly certain, we'll be using npm-scripts at this point rather than something like Gulp or Grunt. I'm also fairly certain we'll default to handling SCSS or similar syntax.

The following is a rundown of some of the CSS-related build scripts that we might utilize. These were copied over from our Slack channel discussion.

What we need to do is come up with a solid set of scripts that would be useful in most theme projects.

Working with the styles:

• https://github.com/postcss/postcss-scss
• https://github.com/ai/browserslist
• https://github.com/jonathantneal/postcss-preset-env
• https://github.com/postcss/autoprefixer
• https://github.com/MoOx/postcss-cssnext
• https://github.com/stylelint/stylelint

Working with the files (probably some crossover with JS files):

• https://github.com/jonschlinkert/copy
• https://github.com/sindresorhus/del-cli
• https://github.com/isaacs/rimraf

[brettsmason]

If it helps I read a nice article on moving from SASS to PostCSS the other day.

I also think Webpack is worth considering. Its pretty much required for JavaScript work these days, and looks like the latest version has been simplified a little to setup.

[samikeijonen]

Also linking conversation in Underscores about linting and compiling.

I haven't tested using only npm-scripts. I'm 100% sure it work for CSS. But not sure about JS, SVG icons, and images.

Let's open separate issues when there is something to test.

[brettsmason]

I've put a bit of work in to getting a full Webpack build chain setup here. Would it be of interest if I finish it off and get a PR setup, or would you rather stick with purely NPM scripts?

If not I'll save it for my own fork as I think I want to go with that solution personally 😄

[justintadlock]

Fixed. See: #22