The first step on our journey is to get PostCSS installed—this runs from Node.js; we can use any one of several task runner plugins to install it. For the purpose of the exercises throughout this book, we will use Gulp; if you prefer, alternatives such as Grunt or Broccoli can be used.
Let's make a start with installing Node and Gulp:

When installing, accept all defaults; this will be sufficient for the exercises throughout this book.
node –v
The output shown is the version of Node that is installed; this is a quick check to ensure Node.js has indeed been installed correctly:

package.json file to store our dependencies for projects. Run this command at the command prompt, and press Enter:npm init
package.json file; enter the details as shown in the screenshot, or press Enter to accept the given default (shown in brackets, after each question):
We now have Node configured and an empty package.json file in place, so let's add our dependencies. We will start by adding Gulp first:
c:\wamp\www\postcss.npm install --global gulp
package.json file we created earlier in step 3 and step 4:npm install --save-dev gulp
Once completed, Gulp is now ready for use; we can go ahead and install PostCSS.
We're at the interesting stage now—installing PostCSS. PostCSS is available from https://github.com/postcss/postcss, and can be installed into Node using a Gulp plugin. Let's do that now:
npm install --save-dev gulp-postcss
If all is well, we should see something akin to this screenshot:

On its own, PostCSS doesn't do anything; to make it more useful, we are going to install three plugins. We will explore using plugins in greater detail later in the book, but for now, don't worry too much about what is happening:
npm install --save-dev autoprefixer
package.json file; if all is well, we should see something akin to this screenshot:
To make it easier to view JSON files in Sublime Text, try installing and activating a custom theme, such as MonokaiJSON Plus, available to install from https://github.com/ColibriApps/MonokaiJsonPlus.
PostCSS is now installed for use, but if we try to use it, we probably won't get very far, as it needs to be configured for use! Let's take a look at doing that now, by creating a simple example that will add vendor prefixes to some sample CSS rules, and automatically minify the results.