Using Jekyll This ain't your grandmas blog engine
So, recently I realised that I wanted to get back into writing my blog in a bit more of a serious manner, so I loaded up my old wordpress blog and I was revolted!. I remembered it being so much shinier than it was, it looked grey and drab, and blegh.
It was hosted on my own set of servers, and I really didn't want that as a long term solution, because of two things really:
- I want to spend as little as possible on hosting becuase, well, who wants to spend money if they don't have to?
- My personal VPS resources aren't great, and it does impact the performance of wordpress from time to time, even with memcached and apc doing their crazy thing.
Ok, cool, so what's this Jekyll thing?
Jekyll is a blog aware static site generator - which is a complicated way of saying that it takes a bunch of text files and smooges them all together to build a completely static site in flat html files. This means you get the advantage of templating, simple post creation, and so forth, from systems such as WordPress and so forth, with the speed and efficiency of doing everything in flat HTML.
The handy dandy thing is that GitHub Pages, the free hosting that is offered to GitHub members, has Jekyll support, meaning you can submit your site in the form of Jekyll source, and it will be compiled into the static site on the fly. The downside with this is that you are restricted to the Jekyll functionality that GitHub think is appropriate. This is, unfortunately, somewhat limited - as it means you don't get the power of the jekyll plugins, however it's completely understandable, they don't want people executing arbitrary code on their servers.
Sounds good, I'm interested, tell me more...
Well, Jekyll can be pretty intimidating if you're unfamilier with it, so you might want to start with a prebuilt helper framework, such as Jekyll Bootstrap or Octopress. However they're really aimed at two different approaches of running a Jekyll website - especially when you're talking about hosting them on GitHub Pages. I'm going to talk about them as if one were thinking of hosting on GitHub Pages.
This is a simple set of liquid templates and logic set up as a quickstart framework for Jekyll. It has a setup to use templates, and some handy helpers and templates to generate archives, site maps, rss feeds, and similar.
Because it is fairly basic in its implementation it means that it is completely compatible with the version of Jekyll that is used for the compilation on GitHub pages, this is its biggest advantage for me.
This is an entire plugin set, template setup, and suchlike that adds a massive amount of functionality on top of the general default Jekyll functionality set, which is pretty awesome!
Unfortunately all this extra functionality means that you can't compile them on the GitHub Pages server, and you must do it on your own machine and then commit the compiled files to the github repository. Since I want to be able to create posts through the GitHub web interface by manually creating the post files, this is probably the biggest disadvantage in my eyes to using Octopress.
So, Jekyll Bootstrap then?
Indeed! That's the plan!
I did a lot of futzing around with the templates in this system so it's pretty unrecognisable as a base Jekyll Bootstrap setup. One of the things i wanted to do was to build a portfolio that was kinda content managed, and not just hard coded. For no better reason than "it looked like fun". This is where I ran into my first hurdle with the system.
Page ordering It's annoyingly inconvenient
One of the issues with Jekyll (at least the version on GitHub Pages) is that there's very little utility for ordering pages within the system. For example - when running a Jekyll test server on my home computer during the development of this site I was able to order the pages purely by using filenames to achieve the ordering - for example:
On my home server - they were delivered in the
site.pages array in that order, so just putting a number on filename was enough to order the pages to my satisfaction.
And here's the rub For in that sleep of death what dreams may come?
Unfortunately, on pushing this to GitHub Pages they ended up being ordered like:
Which is far from what was desired - infact it makes very little sense as to how they were ordered, they weren't even done by created timestamp, or updated timestamp, there didn't really seem to be a pattern at all! This was most vexing, so I was close to just hardcoding the portfolio section of the homepage.
However, I was doing some googling and I came across a pull request on the Jekyll Bootstrap repo, and it was a very handy little solution to my issue. So the code I implemented was:
My mind rebelled at this solution, somewhat, because as a developer more used to dynamic site building doing iterative for loops like this just scream "inefficiency" to me. However since this is done just once when the page is generated I guess I don't really have to worry about that, it's just extra load on the GitHub servers when I push a page updated, and hey, knowing me that's not going to be all that oftan.
Dynamic Content Doesn't this mean you'll lose some niceness?
Well, yes, kinda, it means we don't have the traditional on-demand kind of dynamic things that you get from the server side scripting that I usually embroil myself in. However the nerd in me squeals with barely contained joy that I have to come up with new and interesting ways to solve problems that I typically would have just used some PHP for.
Whilst I would never be able to implement highly interactive features such as forums or a full CMS, there are certainly some things I can implement. The way I see it there are two possible ways to get some of that niceness back, and which one I use depends on the immediacy of the data being presented:
Periodic Data Updates
On my old site I had a script that used a PHP cURL scraper and a MySQL database to track my Xbox Live achievements on my site in a nice way, this means that the data was only changing whenever I scored a new achievement on Xbox Live. That's very doable, and I have infact implemented it already, and I shall document the processes I used more thoroughly in another post.
Instantaneous Data Updates
So... What's your conclusion?
Well, Jekyll bills itself as a blogging engine for coders and, well, I'm not entirely sure I agree, to my mind a coder would write their own blog platform, or heavily customise an existing blog platform. That's certainly what I've always done, which is probably why I've never been able to get a blog running for longer than a few weeks at a time, so I have to say this is the next best thing. Plus the fact i'm going to have to get inventive to do some funky functionality on it, I'm kinda happy about it.
So I'm really looking forward to getting my teeth into this stuff.
Related Posts They might not be good...
- Tech - 7 posts