Brian Bailey Preface to the Revised Edition

Making Friends With Jekyll

This site is built using the Jekyll content generator and hosted on GitHub. I wrote recently about moving my writing to a simple, static site that doesn’t use a database, can be deployed anywhere, and allows me complete control over the content. Here’s how I landed on Jekyll.

My search was limited to tools that use Ruby since it’s the language I’m most familiar with and the community and resources around it are so helpful. The first three options I considered were Nesta, nanoc, and toto. Each has its benefits. Of the three, toto is the most simple and limited (in a good way). Nesta and toto each make it easy to deploy to Heroku, so a version-controlled, free site is possible in about five minutes. I’d recommend trying all of these, and any of many other options you come across, because you never know why one tool will click with you while another one won’t.

I actually found Jekyll because I loved the design of Tom Preston-Werner’s site, the creator of Jekyll. For the past few months I’ve been bookmarking blogs and sites with designs that really appeal to me. Every month, my preferences just kept getting simpler. I just want readable text on a page; no columns, no mixed content, just words. In the end, they are all that matter.

The magic moment was when I realized that Tom’s entire site is on GitHub. Instead of jumping into a tool without any context, I could download the source code and immediately have a working site with great examples of how to accomplish all the elements that make up a site (archives, syndication, navigation). It was a massive help and as you can see, I largely emulated his style and structure.

People who use Jekyll love to write blog posts about using Jekyll, which made it very easy to get up and running. Here are some of the posts I’ve found most helpful:

The beauty of Jekyll and Ruby is everything makes a great deal of sense. When you imagine the most straightforward solution to something, you’re usually right. Having access to the source code of so many different Jekyll sites is a big help if you get stumped. I’ve found that usually getting stumped means it’s not worth it, though. I spent a few hours working with various category and tagging options until I decided that I have no reason for them. And if I ever find myself typing ‘Jekyll sidebar widgets’ in my search bar, well, it’s time to hang it up.

The best part of this experience has been working on it with my son, Ben. He has been experimenting with different site tools as well and fell in love with Jekyll along with me. Over the next week, we spent quite a few hours learning the ins and outs together, customizing our sites, trying new things, and sharing how-tos. He even took his site one step further and is hosting it on Amazon’s S3. You can see it here.

You’ll find the full source of on GitHub. Grab your own copy and then make it your own.