On migrating from Tumblr to Jekyll Bootstrap

I’ve been toying with the idea of moving away from Tumblr for a long time now, having had my own share of problems with Tumblr downtime.

I had made some steps into switching from Tumblr to Octopress, but the steps to deploy Octopress meant that I had to compile all of my pages each time I made a change, and then deploy them using rsync.

I’m now using Jekyll Bootstrap, hosted by GitHub. The steps to deploy are much easier, I just create a new markdown file for a post or page, write content using my text editor, and then deploy to GitHub using git.

Switching to Jekyll Bootstrap and maintaining all of my old Tumblr posts and urls has been a smooth process, I’ll detail this below:

• Setting up a local repository for GitHub pages with Jekyll Bootstrap

  This was really simple, the Jekyll Bootstrap website has some simple steps to get you started.

• Importing my old Tumblr posts

  This required a little bit of work, as I had to update my local copy of gem, but after I had installed all of the necessary gem bundles, importing from Tumblr was as simple as running a one-line command:

  $ ruby -rubygems -e 'require "jekyll/migrators/tumblr"; Jekyll::Tumblr.process("http://www.your_blog_url.com", true)'

  Migrating from other platforms is detailed on the Jekyll migrations page over at GitHub.

• Tidying up the imported pages a bit

  One of the downsides of using a platform that uses a WYSIWYG editor is that the posts end up with a lot of crap markup. So before deploying your imported pages, it’s a good idea to go through the imported pages and tidy up the markup.

• Setting up my subdomain to work with GitHub pages

  Using a custom subdomain with GitHub pages couldn’t be easier. You simply create a file named CNAME with the subdomain you want to use contained in it, and put it in the root of your GitHub repository.

  After you’ve set up the CNAME file on your repository, you’ll also need to create the subdomain with your domain registrar, and point it to the GitHub Pages IP address.

• Pushing your new blog to GitHub

  This is the easiest part of the whole process, pushing to GitHub. Assuming git is already set up on your system, you just use the following commands:

  git add <the new files you've created (use 'git status' to see)>

  git commit -am "A message describing the changes you made"

  git push

After all of that, all that remains is adjust the permalink taxonomy, and creating a custom blog index (such as the one I’ve made) to display the latest posts.

So far I’m really happy with Jekyll, and for now I’m quite happy with using the Twitter Bootstrap style – in time I’m sure I’ll be tweaking and changing the style a bit to align it with my main website a bit better.

Update:

So a day or two after putting the new blog live, I realised that Google had indexed my old tumblr posts with the following permalink structure:

http://blog.omgmog.net/post/XXXXX/post-title-as-slug

but I’m using the shorter version, still valid from the old blog:

http://blog.omgmog.net/post/XXXXX

Which will actually be http://blog.omgmog.net/post/post-title-as-slug for new posts created with Jekyll.

A couple of my posts were high-traffic posts according to Google Analytics, so I had to sort out some sort of redirect for these posts so that the old indexed urls would still function, and visitors would find their way to the new posts. I found a Jekyll plugin called Jekyll Alias Generator which works by just adding a new alias: /path/for/alias to the YAML block on posts. The problem with this though is that GitHub hosted pages don’t allow you to use plugins with Jekyll, so I couldn’t cleanly deploy this by just adding alias to my YAML block and never thinking about it again.

The solution I found for this was to run the local Jekyll server with the rake preview command, so that it would generate the alias pages for each post and put them in the _site directory. I then copied the aliases for the posts I wanted to maintain to a new post folder in the root of my Jekyll repository (mirroring the post structure that I’m using), and then deployed these static HTML-based redirects to GitHub.

I’m not completely happy with this solution as it means I’ve now got a handful of static html files on GitHub that serve no purpose other than to redirect to new pages, but it works.

I’d like if GitHub would allow plugins in some form in the future, or give us some sort of solution for setting up pattern-based redirects, similar to how you would do with a .htaccess file on an Apache webserver.