Reading a few posts about Movable Type on Daring Fireball, kottke.org, and Six Colors, I remembered my short history with Movable Type.
My first CMS on redbin.in was Movable Type but very quickly moved to Octopress and after that to Pelican. I stayed with Pelican in the end.
The reason I ditched MT was that TextMate could not connect to MT. Most
of the posts published on redbin.in were written in TextMate (the first posts I wrote in MT’s interface but I did not like the interface).
I love simplicity when it comes to running a blog. That is why I chose Octopress and Pelican. Both are simple static site generators.
Here is what I wrote about Pelican on redbin.in:
- setting up Pelican is easy (easier than Octopress because has less requirements than Octopress); I’m using Homebrew on OS X and I had to install only Pip (Python package manager), Pelican and Markdown; pelican-quickstart creates your blog, required folders and the config file;
- with Dropbox’s and incron’s help you can post from any device that has an internet connection and Markdown editor that supports Dropbox (the latter is not a problem for computers since you can easily install Dropbox on them; Dropbox support of your editor is more important for mobile devices); most of my posts were written in TextMate using Markdown;
- deploying the new post is really fast (after you save your Markdown file on Dropbox the new post quickly appears on your web site);
- it is a static site generator.
I use Jekyll on cahuk.net now. At some point I realized that Jekyll has more themes than Pelican and because I was looking for a new theme that would fit my needs I decided Jekyll would be a better option.
I think I made a good deal choosing Jekyll.