Django CMS vs Flask
When comparing Django CMS vs Flask, 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 Flask is ranked 7th. 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.
Specs
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 Minimalist without losing power
Flask is very easy to get up and going, with vanilla HTML or with bootstrap pieces. It doesn't take much lines of Python to load Flask to get headers working, etc, and since it's all modular you don't have to have something you don't want in your application.
Pro Lots of resources available online
Flask is one of the most popular Python web frameworks, if not the most popular one. As such, there's plenty of guides, tutorials, and libraries available for it. A large number of important Python libraries, such as SQLAlchemy have libraries for Flask, which add valuable bindings to make the development process and the integration between these libraries and Flask as easy as possible.
Pro Extremely easy to build a quick prototype
Even though it's pretty minimalistic out of the box, Flask still provides the necessary tools to build a quick prototype for a web app right after a fresh install. With all the main components pretty much packed in the flask
package, building a simple web app in a single Python file is as easy as it gets.
Pro Very flexible
Flask gives developers a lot of flexibility in how they develop their web applications.
For example, the choice of not having an ORM, but instead choosing one suited to the task, or another area where Flask gives a lot of options to developers is the templating. They can use Jinja2, Flask's default templating language or choose from a number of different templating languages they desire.
Pro Great documentation
The official documentation is very thorough and complete. Everything is explained in-depth and followed by extremely well-explained tutorials that tackle real-world problems.
Pro Able to use ORM or "true SQL"
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 Not async-friendly
Flask is explicitly not designed to handle async programming.
Con Setting up a large project requires some previous knowledge of the framework
Setting up a large project with Flask is not that easy considering how there's no "official" way of doing it. Blueprints are a useful tool in this regard but require some additional reading and are a bit tricky to get right for a beginner.
The lack of some defaults can also be problematic. Having to choose between different libraries for a certain task is never easy, especially if you have never worked with Flask before.
Con Threadlocals and globals used everywhere
The default way of creating applications in flask makes it hard to use reusable and clean code.
Con HTML-oriented, not API-oriented
Not necessarily designed for making APIs, though that is possible