Most of the groundwork is done, therefore I can finally explain what happend here:
The solution: Running my own blog somewhere safe.
Quest for an alternative
My top three requirements were as follows:
- Small technology footprint
- Access to the source code
- Comfortable way to write posts
Due to my prior knowledge my choices basically boiled down to three options:
- Writing my own blog engine with play! or ruby on rails
- Digging into the world of static blog generators
I don’t want to develop in php, therefore Wordpress was off the table. Writing my own blog engine seemed a bit overkill and to be honest: no one needs another blog engine. Ergo the only valid choice was to look for a suitable static blog generator. Of course many blog engines not written in php exist, but static generation has a few convincing advantages.
Low Tech, High Life
- No ugly user input that has to be dealt with
- Posts are written in your text editor of choice
- No server-side code means less bugs
- Static files scale incredibly well
Posts are written in plain text using Markdown and Jekyll generates static files for the page. Subsequently the files can be uploaded to the web-server of choice. Done. This leads to very appealing workflows:
Currently I’m writing this post in VIM and reviewing the final look in a browser window pointing to localhost. Afterwards I’ll commit the post to a git repository and push it onto github which in turn will compile the post and add the static files to my blog. BAM! Can’t beat that workflow, Wordpress!
I want my own!
To get your own glorious Jekyll blog, have a look at its documentation. The Jekyll website is itself powered by Jekyll and the source code is visible on github for further inspiration. Maybe I’ll write a short tutorial for a nice setup some time in the future. Maybe.