As another poster points out, there aren't a lot of CMS-related posts on HN, but I'd like to share a little of our experience with Django CMS.<p>I've been using Django CMS since early in the 2.x releases (the earliest Django CMS site I still have the code for was using 2.1.0.beta2), and since then we have developed approximately 80 Django CMS sites; with traffic ranging from a few hundred hits a month, to our largest which serves a few hundred thousand hits per day across three languages.<p>In all this time, I still haven't found a compelling reason to switch to anything else. Django CMS's most powerful feature is that it's just plain old Django. This means that it's rare we can't use the CMS as a base framework for a site, and then plug custom applications into the site tree as necessary. Certainly few of our clients have needs which are exotic enough where this pattern breaks down. Yes, this requires a certain amount of learning curve, but it's not insurmountable at all, and I think it's conceptually simpler than most other CMSes out there (I've been an agency-side web developer for 15 years, and I still can't figure out how some people mangle the Wordpress page loop).<p>I was concerned early in the 3.x cycle when front-end editing was introduced (and I believe the introduction was mishandled by the development team), but recent releases have polished this to a level where I can ship it to clients with confidence. This week we launched a new site using 3.2, and content wizards, in particular, are a powerful addition (will these be made multi-step in the future? It would be nice from a UI point of view).<p>The CMS in general is in good hands, though I do worry that without strong community leadership, it might move too far towards being 'the platform which powers Aldryn', rather than a strong stand-alone CMS. Maybe that's too negative, but I do see it as a risk.<p>5 years ago I made a bet on Django CMS, and it turned out good, so I'm happy. Maybe it'll serve the next 5 years.