I've been working with Django for years, and Mezzanine for a year. At this point, I'm tempted to start every site as a Mezzanine setup. Mezzanine provides the "just right" element of CMS support. If I want to hack a few templates, and let Mezzanine handle all the variable content? Np. If I want to get totally custom, and develop a section completely seperate? Np. If I want to borrow a few schema elements and template tags, but that's it? Np.
Several years ago I spent a month experimenting with Django CMS for a project. It was good, but too hard to customize for my application. I put the whole idea of a Python based CMS aside, as the others seemed to cumbersome, immature, specialized or dormant. I even worked on a "home brew" CMS that was tough as nails to develop for.
Then, I came across Mezzanine. At first, the docs were a bit, um, technical where I needed light and light were I needed technical. Fortunately, from the mailing list, I could tell there was a lot of positive and on the nose activity in the direction of sites I needed to create. One net-net is I decided to rework my old PHP base site (YACS, if you're keeping score) in Mezzanine. No dig on YACS, but professinaly I forcibly left PHP in the dust a couple years ago. Well, it took until about now, but I finally put my content where my mouth was.
One thing I vowed to do, after experimenting with half a dozen CMS code bases, is document how I built the site, whatever that entailed. Heretofore and therefore, I present...Share on Twitter Share on Facebook