Hi everybody As one of the contributors of django-cms, we (www.divio.ch) are using the django-cms codebase for a lot of our projects. At the moment we include/integrate non-textual content (galleries, contact forms, or whatever) in the following manner: - create a navigation node. That is a «Page» in django-cms - (optional) create text/html content, That is a «PageContent» in django-cms - link to your custom django models over the Add-on functionality (to be activated in the cms_settings.py, not yet in newforms-admin)
This way, one can include any type of custom models on specific pages. The pages itself are accessible over the navigation. They also - of course - can be reordered over the navigation interface of django- cms. If you have more complex pages/views that not contain any pagecontent you would edit with django-cms, you can still create the navigation node (Page) and i.e. set the «override url» attribute of the Page. Than you can "catch" the overridden_url in your urls.py before the cms url handler comes into play and do whatever you want in your custom view. That's how we do it... Lots of ideas concerning the improvement of such integration are in the pipeline. As we are a small team at the moment, we enjoy if some proposals and contributions are made from anybody out there. Stay tuned... Maik On 9 Sep., 21:31, "Antoni Aloy" <[EMAIL PROTECTED]> wrote: > 2008/9/8 Thomas Steinacher <[EMAIL PROTECTED]> > > Hi Thomas! > > > > > @Antoni Aloy: > > What do you mean by integration? Like integrating other applications > > (e.g. a gallery) into the CMS? We're still looking for a good solution > > to do that (e.g. by providing an API which allows to write a CMS > > plugin which would allow to integrate a third-party app directly into > > the CMS). > > > I divide CMS in applications in two groups, one are just APIs, so you can > > create an application and the CMS just provides the content, but in that > kind of applications textual content is not the goal. So, they are easy to > integrate with your applications but they don't provide much functionallity. > Django-cms would be that kind. > > The other group are CMS applications. That is, the CMS *is *the application. > They are very usefull when your site is content based. Usually this kind of > cms applications don't fit when creating applications that need a CMS. The > user interface for the CMS and the fucntionallity are much better than the > prevoious one. > > I don't know yet where to classify it. In fact I'll be very happy if I could > have a powerfull CMS like yours being able to create applications using it > as a way to manage multilanguage content. > > My english is not as good as I like but this is what I'd tried to say with > "integration". > > -- > Antoni Aloy López > Blog:http://trespams.com > Site:http://apsl.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
