Awood/travis

The Openshift Jenkins instance was not performing well as a CI environment.  The application would get idled which would cause pushes to fail and it would often lose track of the build nodes also causing build failures.  Additionally, Jenkins was not aware that the GitHub repository is the actual upstream so builds could only be triggered by pushing to the Openshift repository directly.

Travis won't get idled, won't lose build nodes, and handles the desired workflow: pushes to master are built and then deployed on Openshift.

As part of this switch, I converted our CSS preprocessing to use Sass instead of Less.  Less is implemented in Javascript which made the build awkward as the build environment needed NodeJS or the like.  Sass is implemented in Ruby and supported seamlessly in Jekyll.

The one downside is that if Travis fails deployment of the site, it does not fail the build so no notification is given of the deployment.  I'm not sure if there is a way to address this currently.  It looks like there are some [feature requests](https://github.com/travis-ci/dpl/issues/143) out for this functionality.