The How and Why of my Move to Jekyll
Today I decided to move my blog from Wordpress to static html files. These files are generated via Jekyll. The first version of this new blog, contains (most) blog posts from the wordpress installation. The included migration script in the jekyll package was used to move all posts to markdown format. All absolute urls to images was changed to relative urls, and all [gist]-shortcodes was changed (via a simple regular expression search and replace in Textmate2) to the standard script-include.
Search: \[gist id=([0-9]*)\] Replace: script tag with the src: https://gist.github.com/$1.js
I have had this move planned for some time actually. I was tired of the constant surveilance and updating of wordpress (and plugins). And I was tired of the tedious creation and editing of posts. Now, whenever I want to create a new post, I just create a new markdown-file in the _posts folder - all content are also stored in a git-repo instead of in databases. All unnecessary software has been removed from my blog - and only a simple nginx server is used for serving the content. The downsides are simply outweighed by the upsides.
I use a simple two (three if you count the shebang line shell script to upload the changes to my blog.
#! /bin/sh jekyll rsync -avz --delete _site/ firstname.lastname@example.org:/var/www/rootDir/
The complete installation of Jekyll, move from wordpress and first deploy took me less than one hour. And I love it already. I may need to do some design work at some point though.