Prompted by security holes in Wordpress that resulted in spam links embedded in my blog, I switched to Jekyll about a year ago. The switch was painful, but the results were good.
A few months later, I switched from Jekyll, which is written in Ruby, to http://blogofile.com, which is very similar to Jekyll, but written in Python. The second switch was prompted by one of the parsers in Jekyll repeatedly choking on bad markup left over from Wordpress, but failing to reveal the location of the parse errors.
I've subsequently used Blogofile for a larger site that includes both static pages and a blog. It's worked extremely well.
Yeah, that was exactly the problem I had-- Liquid error, but no idea what post contained the problem. I ended up doing a binary search by removing half of the posts, re-running Jekyll to see if the error persisted, and so forth.
Fortunately, the switch to another blog compiler is easy once you've got everything as flat files.
A few months later, I switched from Jekyll, which is written in Ruby, to http://blogofile.com, which is very similar to Jekyll, but written in Python. The second switch was prompted by one of the parsers in Jekyll repeatedly choking on bad markup left over from Wordpress, but failing to reveal the location of the parse errors.
I've subsequently used Blogofile for a larger site that includes both static pages and a blog. It's worked extremely well.