Cross Fell, Northern Pennines, UK


The Strange Case of Dr. Jekyll and Mr. Hyde

A first try at using Jekyll

A few weeks ago, I stumbled over Jekyll, a ruby implementation that is geared towards producing ‘responsive’ static websites. The idea of having plain-text posts, which in turn get rendered into nice, clean, fast HTML sites, is really appealing. Why? Have a look at a generic CMS such as WordPress or Joomla. It may have a nice interface allowing you to type posts, add some images and links and saving them online that make it sort-of easy-to-use. The back-end of these sites however is often database-driven (MySQL) and allows for more than any user (/web developer) might ever want and, perhaps more importantly, slowing it down. Too many options and difficult template-adjusting-tinkering-sessions as a consequence.

In my opinion, a website should be clean, concise, simple and mostly text-, image- or link-based. When I occasionally write a post, it’s about music, movies, photos or science (perhaps even sharing code). A resume is a must, as well as a means of showcasing photo’s or projects. I don’t need a big forum, facebook-likeable posts and other what-have-you-not’s. The cleaner, the better. Perhaps a good time to introduce Jekyll.

Jekyll is made with responsiveness in mind. Easy scaling between smallish-phone-size-screens to huge-desktop-screens. The posts are simple plain-text files that get compiled and type-set into a static site, ready to be deployed anywhere.

This website is my first attempt to get a fresh new start. Occasionally things may be broken but the steep-learning curve (in combination with excellent examples of themes, such as ext.link already got me here. Improvements will follow but until then, it seems like a good start. I like it anyway…