Why I switched from WordPress to Jekyll


My web hosting provider, Hostlatte was down for over a week. After they resolved their issues, they restored my site to their backup from before I launched this blog. I provided them with a functional local backup copy of the entire blog that I (thankfully) generated before they went down, and it took them a few tries to get the restore correct.

After the restore, the blog was still suffering from WordPress database connection issues, which I believe was due to the hosting provider still being wonky. I have restored using the backup copy I provided Hostlatte, so the restore should have worked. At this point, my patience and confidence was wearing thin, so I decided I wanted to switch providers.

And so, I stumbled upon a simple static blog generator, Jekyll. Neat thing is GitHub Pages provides free hosting that happens to include Jekyll support!

So in an afternoon, I was able to do the following:

  • Research and install Jekyll
  • Decide if Jekyll was the right tool for the job
  • Setup Jekyll development environment
  • Migrate from WordPress
  • Setup on GitHub Pages
  • Setup custom domain for GitHub Pages

The entire setup process is fairly well-documented, including a very straightforward conversion process from WordPress.

Simple, done, painless. Blog RELAUNCHED!


Comments


Blog Relaunch!


Today, I’m relaunching my blog, this time powered by GitHub Pages and Jekyll!

Cool thing is you can git clone my entire site and have a local copy for yourself! Not sure why you would do this, but the point is that you can!

Side note: Apologies for using the default Jekyll site design, I just wanted to get the blog back up and running first before I make it pretty.


Review: Git Clients for Mac - Tower vs SourceTree


Review: Git Clients for Mac - Tower vs SourceTree

Recently, I have been playing around with Git clients to try to improve my productivity. Here’s a quick rundown on my experience with two Git clients: Tower and SourceTree. I spent 30 days with each client to fully familiarize and evaluate the products.

Before my review, I’d like to rant a little bit about using Git clients:

Using a Git client should not be a way to avoid learning Git via command line; it should be a tool to improve your productivity. Having said that, using a Git client is a great starting point for learning the basic concepts of Git.

It is essential to know your way around Git via command line, as sometimes you may not have the luxury of having a client around. Sometimes doing things via command line is quicker than clicking around on a client. Also sometimes what you trying to do may not exist in a particular client, but can be done via command line.

My quick review lies after the jump.


Comments