Django-CMS is a completely different project from Django and also from Mezzanine. Django-CMS has some nice features, but I am pretty sure it duplicates most of what Mezzanine does. I do not recommend using Django-CMS. I find the code more complicated than Mezzanine's, harder to read, and therefore harder to debug and improve. Admittedly, I have not had to use Django-CMS since Mezzanine came out, so those problems may be gone now.
Learn Django first. The tutorial all the way through once or twice should get you comfortable with the basics and capable of working with Mezzanine. Do not begin to think about a sub-framework such as Mezzanine or Django-CMS until you have made it through the tutorial! Get yourself comfortable with Python, too. If you do not know how to create functions, lists, and tuples in Python, you won't get very far with Django. As Mezzanine-is-just-Django, Django-is-just-Python. k On Mon, Mar 31, 2014 at 1:49 PM, Tameen Malik <[email protected]> wrote: > Yes you are right sir! >> > hmm there are two things i am moving towards Django -cms and > Mezzanine. Should i move to django-cms first to get better understanding > to mezzanine world or both are different? > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
