After having been a regular on WordPress since a rather long time (and a certain Movable Type before that) and having subconciously avoided the simplicity trend in favor of engine-based based solutions (it just sounds heavy, doesn’t it?), it was about time to come to the light side. First-look. Excellent stuff. Generates static pages based on markdown(md) content. Very easy to automate publish-on-compile behavior using git.

Only detail that stood way was the obligation to use markdown. Where doth lie the pb you ask? A large bunch of pre-written locally residing ~org-mode~ files having gotten almost-excited that it was their moment to see publish-daylight. Behold! People had already worked on this particular problem (no, I’m not the only org junkie). Here’s two existing solutions that didn’t make the cut of interest:

  1. org manual’s tutorial: The approach described here is based on configuring org to publish, and thus spit out html files, which jekyll finds no problem understanding.
  2. cinsk/jekyll-org: A rather old approach and thus not compatible with newer versions of org. Moreover, the workflow involves conversion of org to html, which again, isn’t letting jekyll do anything to work on the posts.

Here’s two that did make the cut:

  1. eggcaker/jekyll-org: Uses org-ruby to get the translation done. Runs as a plugin of jekyll to do the work.
  2. jekyll-org-mode-converter: Installs as a gem, does the same thing as above. Provides a very nice documentation in the process.

Only /working difference/ that I’ve observed between the above two is that eggcaker/jekyll-org is capable of handling liquid code. This post was thus written under org-mode and resides nowhere as a markdown or an html file under the working tree. The only problem I’m facing with the usage is a large error message upon compilation (under ruby-2.0.0 and jekyll-3.3.1), which behaves strangely as a warning and doesn’t actually hinder the workflow at all (à voir).

Bref - org pages necessitating a larger canvas than a tweet will find themselves published here.

UPDATE - 22/02/2017 - jekyll doesn’t pick up the post date from the org-file’s filename, as it functions with a classical markdown ‘.md’ post file. org-mode files do get compiled into posts, while picking up the compile date for each one of the resulting posts.