Joeri Jongbloets bio photo

Joeri Jongbloets

Almost MSc // Modeller in the lab // Fluent in Java, Python, and R

Email Twitter

After using a placeholder page as my "homepage" for a long long time, I decided to move on to a real website (one that actual covers multiple pages).

Recently I stumbled upon [this][http://] great website that combined many great things: simplicity, style, R code and build with a new/unknown - at least to me - kind of web framework. The framework or software package that was used is called Jekyll and although it is there for some time it seemed revolutionizing to me.

It is a static website generator; meaning it literally generates a bunch of HTML, CSS and other web resources from a few text files. The pages are then copied to a webserver. Since the webserver only has to serve the static files it works much faster than when pages are generated dynamically with PHP, Rails or Django.

This idea sounded appealing to me so I went for it. After reading some blogs about these static website generators I laid my eyes on Middleman1, since 'flexibility' is to me like honey to a bee. Flexbility usually comes at cost: the initial investment. You need to invest some time before it is ready to work, so I sat down for the weekend.

At the same time I wanted to spend as little time as possible on this website, because well I have other things to do. My (naive) thought was: let's use the same beautiful theme2 as the before mentioned blog. One small problem: Jekyll uses Liquid for templating and I was using ERb in Middleman, and that didn't work out of the box.

Now people that know Middleman might say: you can use Liquid with Middleman! Well, I tried… But I couldn't get it work (because including partials didn't work). So I went on and ported the theme to ERb. There are still some glitches that I need to work out, but for now it is nice.


  2. Called Minimal Mistakes (