Django FlatPages vs Django-CMS

Question

Without going into details, I create a Django site, and I would like to implement a CMS solution, having great flexibility regarding page layouts, navigation and organization.

It will be used mainly for our documentation, and so far I have had a lot of headaches trying to figure out what is happening with the Django CMS.

Can an experienced Django developer recommend using flat pages with tiny_mce?

Answer 1

I'm not a big fan of the "404 validation and then return the result" methods with flat pages, but http://www.punteney.com/writes/django-simplepages-basic-page-cms-system/ can give you enough energy to work flat pages in this scenario without using the full-blown Django CMS.

My approach, as a rule, “builds it big enough,” if only something out of the box does not meet all the requirements for performance, your mileage may vary.

It looks like you are after the wiki?

Answer 2

You can also take a look at comparing CMS applications on the Django wiki and maybe even fill in some missing information.

I heard good things about FeinCMS .

Answer 3

Almost all Django CMS there are born from the need and requirements of the main developers during a project or two. Most of them are too much, some are doing too little. If you are trying to create a CMS so that you can dynamically use the creation of content and site layout, which can be internal or external, you may encounter jumping from one cms to another in the hope of finding the perfect one. Or you can just use mptt or django categories to give you navigation and nested links. combine this with the tiny_mce included flat pages and there you will have a simple cms that will satisfy your requirements. Then you can go and add other things if you need. But if you insist, then try djnago-pages-cms & / or mezzanine, which do what you are looking for, but you will be blocked to use them and build around them.