Date

I just saved 50 percent or more of my career by blogging again (I hope).

So I tried Jekyll, I tried Tumblr, I tried Blogger, I tried Wordpress, I tried even tried using Google Docs (yes I did).

Alas, none of them quite worked out well for me. I don't code ruby so setting up Jekyll was annoying (at the time I had the wrong Ruby version or something). I'm not sure what went wrong with Blogger and Wordpress but I just could not use them for some reason.

I like minimal interfaces, but not the kind that tries to hide everything from you (damn you off canvas nonsense!). I also get confused quite easily by GUIs (Where do I type --help? ).

Tumblr, though perplexing at first offered a simple interface to make a post. I liked, I liked, although when I wanted to get a bit dirty and tweak a few lines of html to embed some iframes things got away from me.

Cue the piles of documentation and how-to guides (blah). So in an effort to once again do this thing I looked into a few static site generators.

Point to note:

The first time I used markdown, I fell in love (Sorry honey). You can structure documents in a way that is easily converted to html but portable as plain text documents.

Seriously, I think all email clients should support this by default and we should all compose email like this, but that's another story. Jekyll was the only static site generator I tried at the time and it does support markup but there was too much friction for me to use it.

So I looked for other static site generators that supported markdown but unfortunately I could not find any that had less friction that Jekyll (at the time).

So I gave up and rangled with Tumblr. I must have made 2 or there posts since. Fast forward to 2014 and I noticed a renaissance of static web sites going on. Like at least 200+ projects. The wonderful thing about it for me is that most support markdown and some even come with pretty sweet templates, at least for blogging.

I narrowed down my selection to Docpad, Hexo and Pelican. Docpad and Hexo were preferred because I do mostly Node.js stuff these days. Pelican however looked better for making documentation sites. Not API docs but docs on how to use the software. Now I say this purely on skimming the docs of each project.

I may have missed some points on Docpad and I did try Hexo but could not find suitable documentation based themes. So I gave Pelican a try for the estore.js docs and I'm liking it so far.

So I decided to try it for blogging too. If things don't work, guess what? The posts are markdown so I can copy them into something else if needed.

Take that Mr. 'My posts are stored in database'!

PS: Oh yeah, this was written in VIM.


Comments

comments powered by Disqus