Change to Jekyll and Github Pages

It seems a lot of geeks with a blog tend to spend more time changing the supporting software and layout of the site more than just writing posts. I am no exception. This weekend I followed in the footsteps of coworkers nirvdrum and graysky and converted my blog to Jekyll. I actually took the additional step of no longer hosting it myself, instead prefering the ease of github pages. Here’s what I did to move away from a self-hosted Typo blog

Fork the mojombo.github.com project

It’s a good example site that is under MIT license (except the content itself of course). Added benefit is you don’t have to mess around with the layout just yet.

  1. Delete all copyrighted content
  2. Change Tom’s information to yours where applicable
  3. Change the CNAME to yourdomain.com

Migrate posts from Typo

I had to make some changes to mojombo’s converter for typo 5+. So, grab my version of jekyll or patch your gem install. Here is the diff

With the changes applied, the migration is pretty straight forward.

Modify permalinks and update feedburner

Modify your permalinks in jekyll to match your old typo install so readers don’t lose their way.

Check in all changes to github

You should change your project name to <github-username>.github.com and commit those chages up to github. Also, FYI you need a paid account for CNAMEs to work on github.

Update your domain’s DNS

You need two entries

  1. A-record yourdomain.com to 65.74.177.129
  2. Cname www.yourdomain.com to yourdomain.com

Add disqus for comments

Since these are static pages, the preferred way to add commenting to your blog is through disqus. Actually, I’ve grown to prefer disqus even if it is self hosted.

  1. Add your website at http://disqus.com/add
  2. Add the generated javascript to the bottom of your post layout

That should be all you need to get started. I’d recommend changing your layout so your blog doesn’t continue to look like mojombo’s blog. However, this isn’t strictly necessary.