"Radiant":http://radiantcms.org/ is pretty good too. It would be worth your while to try each and find what suits you best.
Mephisto is still good for blogging if you want it to run in rails. Though there are couple of arguments that Mephisto is moving slower than Typo, I still think a lot are using Mephisto and are very proactive about it (myself included).
I tried Radiant too, but then again its a content management system. And so I went for Mephisto. There are also a couple of plugins developed for Mephisto already but not yet as much as those that are available for Wordpress.
An interesting alternative that I recently stumbled across is "Jekyll":http://github.com/mojombo/jekyll/tree/master
It bills itself as a "simple, blog aware, static site generator. It takes a template directory (representing the raw form of a website), runs it through Textile or Markdown and Liquid converters, and spits out a complete, static website suitable for serving with Apache or your favorite web server." Jekyll is written in Ruby.
To date, I've blogged almost not at all, mainly because I've been busy working on other things, but this year I'm leaning toward trying to write a bit. It helps organize one's knowledge, and it's a good way to get hints, tips and hard to come by scraps of painfully discovered information out into the world where someone else can find them and save themselves some frustration.
The approach Jekyll takes is interesting to me for a few reasons:
- No database or web application to maintain: Maintaining an SQL database full of snippets of Textile or whatever other markup sometimes seems overkillish for an individual's blog. I'd rather spend my deployment energies deploying real work artifacts.
- Jekyll compiles your markup to static HTML content: Deploying the blog and updates to it should be as easy as doing a Jekyll "recompile" and transferring the generated static content to the destination.
- You can store your posts in a Git repository, thereby letting a version control system handle versioning of the markup. If you've ever tried to implement versioning of raw text that then has to be crammed into an SQL database, or in some cases, even used someone else's existing implementation, this may be compelling.
Here's a brief "piece":http://tom.preston-werner.com/2008/11/17/blogging-like-a-hacker.html introducing Jekyll and its history, by its author.
Savage Beast is a good one. And it seems that working with rails is using it. "Savage Beast":http://www.williambharding.com/blog/rails/savage-beast-20/