Joshua Button v2.0

August 17, 2014

I’ve been meaning to give my site a much needed update for some time and I’ve finally gotten around to doing so this weekend. I think it’s fitting that my first blog post deals with how I’ve gone about developing, configuring, and deploying this new version. Now begins my first foray into blogging like a hacker.

First, I’ll list off some of the problems with the old version (which I’ll call v1 from here on).

I decided to scrap everything and start fresh. My first stops were to the Bootstrap and Jekyll websites (because both projects are still amazing). I learned that there was now native support for SASS built into Jekyll. Bootstrap itself now has an official SASS port as well. Perfect, the two together would be my solution to the LESS build problem.

While browsing the Bootstrap documentation I saw a mention of something new to me called…


Bower bills itself as a “package manager for the web”. Here is an excerpt from their website:

Bower works by fetching and installing packages from all over, taking care of hunting, finding, downloading, and saving the stuff you’re looking for. Bower keeps track of these packages in a manifest file, bower.json. How you use packages is up to you. Bower provides hooks to facilitate using packages in your tools and workflows.

Using Bower, I am now able to install a dependency, for example jQuery, like so: bower install jquery. The package is then stored in /bower_components.


I now have a better way to manage my front-end dependencies, I use this to install both jQuery and the official Bootstrap SASS port.

JSON Resume

When it came time to update the resume I decided to check out a project I heard about a while back called JSON Resume. The idea is to have a standard JSON Schema for resumes defined so that the community can come together and easily build themes. This would allow you to quickly modify the appearance. I liked the idea, so I gave it a shot.

When you break it down, it’s just a schema and a Handlebars template along with a CLI tool. I liked it, but there were a couple of problems.

Problem 1

As of now there is no way to use the resume-cli utility on a theme stored locally, everything works through their theme server. This didn’t really work for me as I had created a custom resume theme specific to myself and did not wish to post it to their service (which is just NPM by the way). I was able to write a script which would generate a themed HTML resume locally, but that led me into another problem.

Problem 2

I would now need to be sure to run this export script whenever I updated my resume. On top of that, I needed to be sure that my dependencies installed with Bower could be copied over on a deploy. This led me to the next tool I learned about called…


Grunt is a Javascript based task runner. There are a bunch of plugins which help make it easy to take care of any task our Jekyll site needs. After reviewing the documentation, I created a Gruntfile along with my required tasks. These tasks include:

Now with one simple command I am able to automate all of my required build tasks before I deploy. I could even make deployment a one command process with this tool.


I’m very happy with how this turned out. I now have a more solid base to build off of and everything looks so spiffy and clean. Compare it to the old version for yourself

Version 1 of

Version 1 of resume