Many of my posts are related to my development workflow using Gulp (eg. 1, 2, 3, 4, etc.), and the code in these posts tends to follow a familiar pattern: Install a plugin with NPM Require the plugin at the top of the Gulpfile Add a new task or update an existing one that uses the new plugin…

Shockingly I’ve managed to write 3 posts about PostCSS (1, 2, 3) and not yet mention the truly amazing autoprefixer plugin.  This is easily the most popular plugin, and used by the likes of Twitter, so well worth checking out. Essentially what it does is allow you to write your CSS without using (or even thinking about) any…

I recently wrote a post about next gen CSS using Gulp about how you can write the latest CSS code and use Gulp to transpile it into more widely supported CSS using  cssnext. Another neat feature that I like using is partial stylesheet files.  This is kind of like having separate stylesheets that you concatenate together…

I really hate the phrase “next gen”, it’s heavily overused and usually means that something derivative has been created, rather than something innovative.  But in this case, I am referring to some of the newer features of CSS3 which aren’t supported by all browsers yet, and how Gulp can allow you to use them now,…