For the first post on my new site I figured it would only be appropriate if I wrote about how I went about creating the site in the first place. It was a bit of a journey experimenting with different platforms, but I ultimately ended up with Jekyll and I’m glad I did. Let me tell you why.
My roommate, Jeremy Franz, initially turned me on to Jekyll Bootstrap and Octopress as some good options for a blogging platform that are easy to set up and deploy at no cost through GitHub Pages or Heroku. I set up both, but quickly found that the assumptions and out of the box styling of the frameworks end up causing more trouble than they’re worth for what I was trying to do. If you need a blog in a snap, that’s the way to go, but I knew I wanted to write mine from scratch.
I wanted something simpler, so I dug deeper into using just Jekyll. Jekyll is described as
“a simple, blog aware, static site generator. It takes a template directory (representing the raw form of a website), runs it through Textile or Markdown and Liquid converters, and spits out a complete, static website suitable for serving with Apache or your favorite web server.”
Markdown, so hot right now. Sounds like what I’m looking for.
Jekyll just makes sense for designers. It uses the Liquid Templating Language which is about as simple and human readable as it gets. There’s also a nice little wiki made just for us dumb designers. Throw in a few lines of liquid and your static site will be faking dynamic content in no time!
If GitHub feels foreign to you, not to worry. We’re just going to have to take a few steps back before we start. There are some prerequisites like XCode, Git, Ruby Version Manager (RVM), and Ruby that are necessary just to get your development environment up to speed. Here’s a comprehensive guide that covers a few different versions of OSX. If this is all new to you, don’t be afraid of the command line. It will be uncomfortable at first, but that will pass. Comfortable is what we’re aiming for, not expertise.
Jekyll for Designers
Now, for the scary part. Setting up Jekyll and the designer dreaded command line. Don’t worry, it will only hurt for a second. A great place to start, as with anything, is with the original Jekyll Documentation.
I created a public repo on GitHub named after this post called Jekyll For Designers. It has the basic base code and instructions for getting Jekyll up and running and deploying to Heroku, easy as pie. Also, all of the code for this very site using Jekyll is available on my Muke.me repo for reference. If you run into a dead end, see how I did it. After all, that’s how I made it through my initial setup.
After forking the Jekyll For Designers repo head to the local project directory on your machine in terminal and run
Now you have all of the necessary gems installed that were listed in the Gemfile you forked. To compile your site and see a preview run
Head over to http://localhost:4000/ to see “Hello World”
Your Jekyll install is up and running and ready to deploy! You will need to have git and heroku command line tools installed in order to deploy. These are available in the Heroku Toolbelt if you don’t have them already.
heroku create -s cedar --buildpack http://github.com/mattmanning/heroku-buildpack-ruby-jekyll.git
Push to heroku
git push heroku master
Jekyll to GitHub Pages
If you want to deploy your Jekyll site through GitHub Pages instead of Heroku, then there are plenty of good resources out there for that. After all, that is what Jekyll was created to do. Jekyll Base by Daniel McGraw should do the trick.
Now, That Wasn’t So Bad Was It?
The command line can be scary, but with some experimentation and a little courage you’ll be deploying like a boss in no time. If you want to make Jekyll real fancy and write posts in the browser, check out Prose. It’s like a CMS style backend for GitHub repos.
There’s plenty more to be learned to master Jekyll, Liquid, and Markdown. Here’s some further reading and resources I’ve found useful in my random walk.