Django for CMS, Part 2

I have previously had doubts about the benefits of using Django as a framework for a CMS. I still have my doubts but after working with Django I might be about to change my mind.

The last year or so I have completed 4 projects using Django. 3 out of 4 projects was completed in time with a result that satisfied the customer. All 4 projects of cause of a higher quality that could be accomplished without the use of a framework.

But Django is not an easy framework to use. Even though the basic usage of the framework if simple, it takes time to master more complex tasks. Or what really takes time is to research the topic and discover the correct way to handle the task from within the framework.

But non the less, it's a greate framework!

So, why choose Django as the framework for a CMS? Here are some points:

1. It's easy to catch and URL and map it to a page-like object.

2. There are more and more "off the shelf" plug-and-play Django applications which could easy be integrated into the CMS.

3. Easy to write new CMS extensions as just another application.

4. Build-in json generator to ease communication with client side javascript.

So, after I have really gotten to know Django I feel that it might be the right choice for a CMS. And as Django is slowly getting to a stable version 1.0 and having got the Google stamp of approvel (used in Google App Engine), it might just be time to start.