jsoxford.github.com

This is the source for jsoxford.com - it’s a static site that is generated with jekyll.

Getting started

note: if you’ve got a small tweak to make, just edit the file directly in github and send us a PR, you don't have to worry about installing anything

Requirements:

• a Ruby environment (hint: rvm or rbenv are handy)
• bundler

# install jekyll
bundle install

# run the server
bundle exec jekyll serve

You should now be able to visit http://localhost:4000 and see the JSOxford site.

Building an optimised version of the site

The version of the site up on jsoxford.com is optimised to make it quicker to load - you can build that locally with grunt.

# get the grunt task runner
npm install -g grunt-cli

# install grunt/node project dependencies
npm install

# build a static version of the site
grunt build

# optimise it
grunt optimize

Now _site/ will contain an optimised version of the website, similar to jsoxford.com

If you’re feeling really adventurous, you can deploy it like so:

grunt deploy

Though you shouldn’t need to, we build automatically on Travis.

We’d love for you to make the site prettier/faster/more accessible, just fork and create a pull request (and check out our contribution guidelines.

Travis

We continuously build the site using TravisCI. The config is in .travis.yml. If you’re porting this code to a new repository you’ll also need to replace the two encrypted environment variables:

travis encrypt GH_LOGIN=YOUR_GITHUB_USERNAME —add
travis encrypt GH_TOKEN=YOUR_APPLICATION_TOKEN —add

We have a Tron-ci job to trigger a build every day at midnight, so scheduled pages and/or any time-sensitive preprocessing can occur without us having to modify the repository.

Requirements

To build this site you’ll need Ruby and Bundler installed (gem install bundler) as well as a newish version of NPM.

Content stuff ——————

We link to @jsoxford with twitter intents, so maybe you can use that too? Or not I guess.