Common steps to deploying your mezzanine project
We had a project that needed a flexible prebuilt blogging and content management system. We have worked with a number of other systems, and decided to give Mezzanine a go. We love python as a programming language due to its expressiveness as well as all of the tools available for doing things like scientific computing. The project was fairly simple, but we had one restriction. We had to use a shared host to deploy our mezzanine project.
If you're not familiar, check out their homepage. They have pretty good documentation, and when we were working with it, they made many improvements that went above and beyond what the django core offered. Mezzanine comes pre-packaged with some things like a fabric script to automate the configuration of a new virtual machine if you're running your project on a VPS, and some nice things that we felt that django should have included - like definitions in the settings that find the absolute path to the project directory so you don't have to hard-code things like that.
For this project, we were restricted to a shared host. We were fortunate that the shared host had unusually good python support (Webfaction) - so we didn't have to do too much extra work, but here are a few resources we found.