Vodenski.com
This site runs on django-cms, for two reasons. First, I want to be able to produce content without getting bogged down by templating syntax or XHTML; this site isn't a blog and, anyway, I need more control than WordPress could give me without having to learn its heavy-weight template system. Second, I want to be able to roll out sites for clients in no time and have the option to allow them to control their content without writing a CMS myself (the exercise would be fun at first, but really why reinvent the wheel?).
So far, django-cms has been great; the only thing it lacks is fine-grained access control. Use case: the client wants to be able to edit any part of the site, and wants some of his employees to be able to edit some specific pages in specific ways. The 'specific ways' part of the use case is already part of django-cms--it allows control on a per-plugin basis--but pages are all-or-nothing.