Confused...Django vs Django CMS/Wagtail and value of 'CMS' vs plain Django framework?

[fire base]

I have been learning and building a Django framework website and it is going nicely. The site will be used internationally but largely is a series of specialized forms collecting and manipulating and outputting data to be searched - not presenting changing  'content' per se.

I had seen references to Wagtail and now Django CMS.... is there any reason why I should switch to Django CMS vs just continue building in Django framework?

If there are good reasons to refactor/switch, can I simply import models/views/urls/forms, or some such, into Django CMS or Wagtail?

Can I add middleware to turn Django into Django CMS?

What are the Use Cases for Django framework that put it over a 'CMS'?

 I have searched extensively but not found answers to these qs...

Many thanks.

[Roger Gammans]

Hi

Move Wagtail and and Django-CMS are applications you install in your INSTALLED_APPS setting settings.py to add CMS functionality to a Django project, so you can use these applications as you only app in django projects, or alongside your own custom apps, or other downloaded apps.

Django cms add some middlewares ( Eg, lines in the MIDDLEWARE setting) as it needs to be able to inject the editting tools if you've got the appropriate permissions. I'm not sure of the top of my head about wagtail. But in principle you can either to any django project by imported them and and making the relevant changes to settings.py

The use case for Django without a CMS, is exactly that, you don't need CMS functionality.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e942381f-e48e-411a-8de4-633e524581cdo%40googlegroups.com.