Pablo Iranzo Gómez's blog

mar 16, 2015

Jekyll and MarkDown

For my work I've been using markdown for a while, it allows to use some formatting on the documents created (mainly for knowledge base and solutions) without too much hassle for the formating.

On the other side I was willing to improve the ability to make it easier to post new entries to blog without having to wait too much time, and of course, be able to prepare them offline and then push them live.

  • Using spip allowed me to focus on text without caring too much about formatting, the CMS is not hard to administer, maybe not as popular as wordpress, joomla lately, but definitely, good for the work it's intended to do, and not like traditional webpages.

  • Using blogger, formatting was also not a hard part, and being a good platform improved the availability of tools, but still required online access, and the firefox extensions for it, were still not convinging me for daily usage.

Yesterday, while I was reading some information about github, I got back to their 'hosting' solution (github.io) and like the idea of pushing the code via git (I love the offline commit and later push of all changes), and started reading about Jekyll and Poole.

Jekyll and Poole enhance the creation of webpage posts using MarkDown with some automation for automatic generation of links, reusability of common elements, etc which creates a set of static pages, fast to serve, upload, etc.

I've also used Jekyll-Import to gather my old posts at blogger and I will still convert some of them to markdown and try to get back the auto-code coloring I had inplace (using external JS library).

Well, let's see how this goes and will try to implement some template to website not to use the standard one soon.

PD: This was being written while offline at the aiport on a trip to Helsinki ;-)

posted at 09:06  ·   ·  jekyll