When comparing Django CMS vs Wagtail, the Slant community recommends Django CMS for most people. In the question“What are the best Python based CMSs?” Django CMS is ranked 1st while Wagtail is ranked 2nd. The most important reason people chose Django CMS is:
Django CMS is a very mature project, with many core developers working on it constantly and adding new features and bug fixes.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Mature
Django CMS is a very mature project, with many core developers working on it constantly and adding new features and bug fixes.
Pro Can integrate with existing apps
Django CMS is more of a Django plugin which can easily be integrated with any Django app to add CMS functionality to it.
Pro Double click to edit
You can double click items to edit them or add pages directly on the website (as long as you're logged in as admin). It simplifies content creation and touch-ups.
Pro Easy to extend
Documents are organized in a tree. You can either create new content area type, new tree nodes, integrate complete existing Django app in the tree, etc. It's pretty easy usually.
Pro Internationalization (multi-language) support
Having a website in more than one language can be very challenging and DJango-CMS supports it well. Switching between languages while keeping on the page for example.
Pro Extendable
Although Wagtail comes with only the most basic features, it's by no means an incomplete CMS. It's very extendable and it's up to the developer to choose how to extend it.
Pro Lightweight with the most useful functionalities
Wagtail is a simple and lightweight CMS with the most basic and useful set of features baked in out of the box.
Pro Great separation between developers and editors
Wagtail has the perfect separation between developers and editors. It allows you to construct a site with minimal fuss with features like the awesome stream field and hand it over to virtually any content editor. You can build the site with no knowledge of Django and with the simple interface require no training to get started.
Although this will always require developer time, with 2 or 3 days you can quickly get up a boilerplate site that will fulfill 80% of any site you will develop. Leaving only the bespoke parts to do.
It also nicely slots into any Django project with no fuss.
Cons
Con May be an overkill for a simple blog
Django CMS project is a large and complex project, comparable to Wordpress. As such, it may be too much for a simple personal blog considering that it has many features that may never be used in that particular occasion.
Con ImageChooser widgets dont fully work in sub panels
Con You need to be experienced in Django to get the most of it
Installing Wagtail on a remote server is a little more complicated than FTPing a bunch of files. Furthermore there's no ecosystem for plugins and themes so it can only be fully extended by a developer experienced with Django.