Moving to Jekyll and GitHub Pages

3 min read.

For the past few years my old blog has served me pretty well, but I’ve been looking for something simpler and less cumbersome to update and maintain. I’ve just finished moving my content to a new home, which is now hosted on GitHub Pages and powered by Jekyll.

Jekyll is a popular static site generator written in Ruby. It takes a template directory and then processes it to create a static website consisting of pure HTML files, which you can then host on your chosen web server. Here are a list of reasons why I made the decision to ‘go static’:

Authoring new content

No more bloated CMS or WYSIWYG editors! I can write draft content using Markdown, which can be processed directly by Jekyll. With cross-device apps like iA Writer and cloud syncing via Dropbox or iCloud, writing draft content is now much easier.

Built-in version control

Because this site is hosted on GitHub, version control comes baked-in. I use one branch (master) for hosting the static site on GitHub Pages, and another (admin) for the source.

Performance & reliability

No more PHP/MySQL database means pages load faster and the site should be able to handle periods of heavy traffic with less worry.


Having to deal with mySQL security issues should be unnecessary for something as simple as a personal website or blog. Now I no longer even need think about it.


Because the source for this site is available on GitHub, people are free to make suggestions and/or corrections to my posts via submitting a pull request or opening an issue.


Moving a static site to a new web server in the future couldn’t be simpler. I also still retain the original content in markdown format, instead of being locked away inside a database file.


There are a wealth of good Jekyll plugins available via the community. Jekyll also works very nicely with the Python syntax highlighter Pygments, which you can see in use on this site.


I’ve been using CSS pre-processors such as Less and Sass/Compass in work projects for a while now, so this was also a good opportunity to start again from scratch with my personal site (which at the time was still all hand written CSS) and integrate it into the build process. I’ve chosen to use Sass as I like the syntax, as well as the wealth reusable patterns and mixins offered by Compass.


So far, I’m really enjoying the simplicity of having a static site. Getting Jekyll up and running correctly was quite simple, but I’m still learning a lot about making the most out of my template structure and there is still a lot I need to explore. The new site is by no means complete, but I’m pretty happy with what I’ve managed to put together in just a couple of days.

Scroll to top