Initial commit
Restructure css to use sass

Include susy for grids.
Make use of built in sass compilation.
Install jekyll locally to prevent conflicts with susy's version of sass and jekyll's
Add bourbon
Remove most template styles and template html

Add solarized light syntax highlighting css
Fix gem dependencies so that compass plays nicely

Compass' Gemfile.lock had an old version of listen in it that it wasn't using which conflicted with
the listen being used by Jekyll.  Pointing at stable on github fixes this
Add compass scss generator so that gems that use compass can be imported in the sass
Compress compass sass compilation
Ignore css folder as it now is just compiled sass
Move Sass assets to bower

This removes the compass dependency and cleans up the Gemfile.
Use Sass to compile scss instead of compass by adding the
bower components to the sass path. This hooks into Sass compilation by
Jekyll.
Add normalize css

Normalize the css before styling
Move bower components to _app

This will prevent them being included in the jekyll build in _site.
Normalize css before styling

Use normalize-css.scss to normalize css before styling so all browser
start with the same styles.
Add basic typography scaling for a mobile breakpoint.
Add normalize scss that is being maintained

Beats maintaining myself
Remove white space
Add layout breakpoints

Create a map for each susy layout with its breakpoint in the form:
$layout: (susy: (susy-settings), breakpoint: (breakpoint-settings));
Use sassy-maps to do a deep get on the nested maps.
Credit to @metaskills for the structure
Remove unecessary sass require

Jekyll is already doing this
Move bower components path

Ignore bower components from build as well as bower.json.
Add bower component paths to sass path

Add components to sass path such that each component can be referenced
with a sass import with just its name instead of the full path.
Simplify adding bower components to sass path

Make use of .bower.json file for each component.  This file specifies
the main directory, which is the file we will want to include.  Use this
path rather than trying to guess the path based on the component name
(this guesswork approach is what we were doing before. it worked but it
may not work for non uniform components)
Create blog post on setting up Varnish Cache

Run varnish cache locally in development environment tutorial.