Guido Flohr

LSI for Jekyll can get slow and did not produce satisfying results for my site. I therefore wrote my own little, largely simplified plug-in hand-tailored for my needs, that does the same job quite well and quite fast.

The static site generator Jekyll stores tags site-wide. You need a little Ruby code if you want to want to maintain them per-language instead, as you would want on a multi-lingual site. In a previous post "Multilingual Web Sites with Jekyll" I had described how to set up a site with Jekyll supporting documents in multiple languages. One thing that was still missing was support for tags respectively keywords.

The main motivation for developing the imperia view processor was frustration about the existing templating engines available for Perl at the time. None of them offered all of the features that I considered a must for the V in the imperia MVC framework. Some of the more important design decisions behind it are outlined below, giving you some insight into the anatomy of a modern template processor.

After waiting years on my TODO list I recently decided to tackle the project "web site". Since I no longer work for Imperia I was looking for a light-weight alternative. I did not want to install PHP on my server, ruling out a lot of options. A colleague finally recommended Jekyll. Its simple semi-static approach reminded me of Imperia and I decided to give it a shot.