If we look through our Gulp task file carefully, there should not be much in there that comes as a surprise—many of the tasks used are ones we have used on many occasions throughout the book.

The key here, though, is that whilst we can run the standard processor that we've already used before, it's unlikely to suit all occasions. It's more likely that we can use it as our base (as stated earlier), then add any extra plugins as needed. The great thing about this is that most of the configuration work is done—it keeps a consistent approach to our work. All that remains is to install any plugins that we don't already have in place—we of course have most of them, but need to install three additional ones, as highlighted here:

gulp.task('styles', function () {
  return gulp.src('src/*.css')
    .pipe(postcss([ rucksack({ fallbacks: true }), autoprefixer(), shortcolor, nesting, pixrem ]))
    .pipe(gulp.dest('dest/'));
});

These have to be accompanied with the relevant calls at the top of our Gulp task file:

var nesting = require('postcss-nesting');
var shortcolor = require('postcss-short-color');
var pixrem = require('pixrem');

In turn, these plugins are as follows:

We can of course add others, and continue converting our code—there are other instances where Nesting can be applied, such as in the rules that control styling for our navigation. The key here, though, is that success is measured in how much we have to change our processor's default setup—in this instance, we didn't have to change it at all! We of course added extra plugins that required a change to one line of code in the processor, but none of the other tasks required any changes at all.

It's at this stage that we have effectively completed the journey to create our processor—well, strictly speaking, our journey should always be considered without end; this will help ensure our tool remains up to date. This aside, though, there are some useful tips we can use when creating our processor, so let's take a moment to cover these in more detail.