Slushie, the pre-packaged gulp pipeline that just works

A few days ago, I was working on a development pipeline tool for the Live team at BBC Sport. A tool that will essentially hook into their existing development pipeline, and provide a pre-opinionated workflow for processing Sass files. It’s a fairly simple concept, but one that would hopefully give the front-end architects a chance to define a set of development rules in one place, and iterate on it, that the rest of the developers can leverage without having to worry about any finer details.

How to lint your Sass/CSS properly with Stylelint

Stylesheet linting. Not many people do it. Many more people should—especially diverse teams that have a lot of hands touching the codebase.

In this article I’m going to talk about why we should lint our stylesheets, and how to implement stylesheet linting into our build pipelines for both vanilla CSS and Sass.

Year Review 2015

Wow, it’s been a while since I’ve written anything on here. I’ve been so caught up with commissioned work, that I really let a lot of things slip in the second half of this year. Last year, I set myself a fair number of goals to complete this year, and the big question is — did I achieve them?

Using Bower install hooks to automate changing CSS files into SASS files after installing them

Have you ever tried to import a CSS bower component into your SASS/SCSS workflow, with the intention of physically importing the contents of that file in to your main.scss file; only to find that the file is linked/referenced and ignored during the build process?

Optimise Typekit for mobile and improve your Page Insights Score

Here's two pretty interesting things you can do to optimise Typekit for mobile and improve your page insight score.

Using Grunt and Gulp together on the same project

Sometimes, just sometimes,you need the power of both in the same project...

What I learned in January 2015

As part of my New Year plans for self improvement, I’m going to take up a monthly retrospective. It’s something I got used to doing while working with the BBC Taster team, and I quite like it. Essentially it’s a look back on a given time period; you jot down what went well, what went bad, and what made you angry. The good is celebrated, while the rest is actioned for improvement during the next time block. At the BBC, we had retrospectives every 2 weeks, but since it’s just me, a month will do fine.

Announcing BBC Taster

As a digital supplier for the BBC, I’ve been fortunate enough to work on a few BBC projects over the last 2 years.

Older ›