CMS
CMS (Content Management System) software applications are designed to manage and publish digital content, such as websites, blogs, and online stores.
Search & Filter
| Package | Wagtail CMS | django CMS | Mezzanine | feinCMS | CodeRed CMS | puput | Django page CMS | django-widgy | django-fiber | feincms3 |
|---|---|---|---|---|---|---|---|---|---|---|
|
Description
|
A Django content management
system focused on flexibility and user experience |
The easy-to-use and
developer-friendly enterprise CMS powered by Django |
CMS framework for Django
|
A Django-based CMS with a
focus on extensibility and concise code |
Wagtail + CodeRed Extensions
enabling rapid development of marketing-focused websites. |
A Django blog app implemented
in Wagtail |
Official Django page CMS git
repository |
A CMS framework for Django
built on a heterogenous tree editor. |
Django Fiber - a simple,
user-friendly CMS for all your Django projects |
feincms3 provides additional
building blocks on top of django-content-editor and django-tr… |
|
Category
|
Framework | Framework | Framework | Framework | Framework | App | App | App | App | App |
|
Using This
|
110
|
187
|
131
|
50
|
0
|
11
|
14
|
3
|
21
|
0
|
|
Python 3?
|
Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
|
Dev Status
|
Production/Stable | Production/Stable | Production/Stable | Production/Stable | Unknown | Unknown | Production/Stable | Beta | Production/Stable | Unknown |
|
Version (PyPI)
|
7.3.1 | 5.0.6 | 6.1.1 | 26.2.1 | 6.0.0 | 2.2.0 | 2.0.13 | 0.9.2 | 1.10 | 5.5.0 |
|
Stars
|
20,308 | 10,636 | 4,830 | 1,089 | 761 | 659 | 286 | 330 | 665 | 104 |
|
Forks
|
4,517 | 3,198 | 1,609 | 238 | 151 | 162 | 107 | 52 | 112 | 12 |
|
Commits
|
|
|
|
|
|
|
|
|
|
|
|
Updated
|
1 May 2026 | 4 May 2026 | 19 Apr 2026 | 11 Feb 2026 | 12 Sep 2025 | 7 Apr 2025 | 28 Jan 2026 | 20 Feb 2026 | 19 Mar 2024 | 30 Mar 2026 |
|
License
|
BSD-3-Clause | BSD-3-Clause | BSD | BSD-3-Clause | Custom | UNKNOWN | BSD | Custom | Custom | BSD-3-Clause |
|
Links
|
||||||||||
|
Feature Comparison
(click cells to edit)
|
||||||||||
|
508 compliant?
|
|
|
|
|
—
|
—
|
|
—
|
|
—
|
|
Demo
|
A feature complete demo package is provided for easy local installation - https://github.com/wagtail/wagtaildemo
|
cloud based demo at http://demo.django-cms.org/
|
—
|
—
|
—
|
|
—
|
|||
|
WYSIWYG Editor
|
|
|
|
|
—
|
—
|
|
, widgy provides a custom drag and drop editor, see http://docs.wid.gy/en/latest/design/javascript.html, it's extensible and can be used to create powerful things, like Forms and Maps.
|
|
—
|
|
Page Depth
|
Unlimited
|
Database limited using django-treebeard
|
Unlimited, using a single DB query.
|
Database-limited using django-mptt
|
—
|
—
|
Database limited using django-mptt
|
If using the widgy-mezzanine plugin, please refer to Mezzanine.
Otherwise, there is a 64 level depth limit on the content of a page from the django-treebeard MP_Node implementation |
Database limited using django-mptt
|
—
|
|
In-line Editing / Frontend-Editing
|
|
Inline editing on the site
+ Frontend editing |
|
|
—
|
—
|
|
|
|
—
|
|
Page Sorting
|
Via visual interface (uses a mobile device friendly paradigm instead of drag-and-drop)
|
Drag'n'Drop
|
Drag n drop
|
Drag'n'drop
|
—
|
—
|
Drag'n'Drop and normal click
|
—
|
Drag'n'Drop
|
—
|
|
Plugins
|
Most enhancements are code reviewed and rolled into the core. 'Contrib' modules include static site generation, sitemap generation and frontend cache validation management.
|
|
Extendable content types and seamless no-config integration with external Django apps. Check out the Mezzanine grid on Django Packages: http://www.djangopackages.com/grids/g/mezzanine/
|
Core design philosophy
|
—
|
—
|
by subclassing a placeholder
|
all widgets are just Django models + a template, all of the widgets are actually implemented as contrib apps. Here's how to write a widget: http://docs.wid.gy/en/latest/tutorials/first-widget.html
|
Django Fiber itself can be considered a plugin for Django, which we believe is the right way to go.
|
—
|
|
Tests
|
|
|
|
|
—
|
—
|
|
|
|
—
|
|
Pypi Installable
|
|
|
|
|
—
|
—
|
|
|
|
—
|
|
Documented
|
|
|
|
|
—
|
—
|
|
|
—
|
|
|
Multisite
|
|
|
|
|
—
|
—
|
|
provided by Mezzanine if using the widgy-mezzanine plugin
|
|
—
|
|
Multilingual
|
|
|
Multi-lingual interface and multi-lingual DB content
|
|
—
|
—
|
|
|
|
—
|
|
SEO
|
|
|
|
|
—
|
—
|
|
—
|
|
—
|
|
Granular Permissions
|
|
|
|
Easily buildable using request processors.
|
—
|
—
|
|
, permissions down to the widget level
|
|
—
|
|
Revision
|
|
|
—
|
|
—
|
—
|
|
, with django-reversion
|
—
|
|
|
Tags
|
|
|
|
|
—
|
—
|
with django-taggit
|
—
|
, with something like django-taggit
|
—
|
|
App Integration
|
|
|
|
|
—
|
—
|
|
, django-widgy is just an app, additionally if you wanted to add apps into the Mezzanine page tree, check out widgy.contrib.urlconf_include.
|
Django Fiber itself integrates with Django, so it's the other way around. This means the full power of Django can be used for apps, and Django Fiber will play along nicely.
|
—
|
|
Test coverage
|
87%
|
70%
|
83%
|
—
|
—
|
About 90%
|
—
|
75%
|
—
|
|
|
Django Versions
|
All supported versions
|
All
|
Mezzanine 4.2.3 supports Django 1.10
Earlier versions date back to Django 1.1 |
1.4.x
1.5.x 1.6.x 1.7.x |
—
|
—
|
—
|
1.4 - 1.6, 1.7 support is limited by Mezzanine
|
1.4, 1.5, 1.6, 1.7, 1.8
|
—
|
|
Multi-device
|
Editing UI is fully responsive
|
|
|
—
|
—
|
—
|
—
|
—
|
|
—
|
|
Moderation Workflow
|
|
|
One-step draft/published and pre-dated publish
|
—
|
—
|
—
|
in a very basic way
|
—
|
—
|
|
|
Media asset merging and compression
|
|
Can and should be handled by 3rd party apps such as django-filer
|
Built-in optional integration with django-compressor
|
Asset collection from content types / plugins: Yes
Compression: No, should be done in 3rd party app |
—
|
—
|
—
|
—
|
using django-compressor
|
—
|
|
Continuous Integration
|
—
|
—
|
—
|
|||||||
|
List of Sites
|
Case Studies: https://www.django-cms.org/en/case-studies/ |
Gallery of over 250 sites: http://mezzanine.jupo.org/sites/
|
Almost everything here: http://www.feinheit.ch/portfolio/projekte/
|
—
|
—
|
—
|
—
|
—
|
||
|
Main focus
|
Wagtail was created to offer maximum flexibility for developers and the best possible experience for content editors and creators, with powerful best-in-class core functionality which ranges from integration of ElasticSearch to automatic feature detection for intelligent cropping of photos.
https://janjislot.org/ Wagtail's editing interface is entirely independent of Django Admin / Grappelli. It has been custom designed for optimal user experience, and it is lightweight, responsive, and fast. Although it will happily power a blog or small website, Wagtail is a compelling choice for large-scale and enterprise projects. It can be used to implement websites of any size, scaling to cope with many thousands of pages (for example http://www.rca.ac.uk, which has over 10,000) and incorporating high end features like native support for automated cache invalidation for frontend caches such as Varnish, Squid, etc. |
Django CMS is built to be extended because every page has other requirements. Our focus is on the most flexibility for the developer AND the content manager.
|
Redesigned interface on top of Django's admin (all your third-party apps supporting Django admin will still work!) for managing a hierarchical page tree, with page types extendable via core API.
Included page types range from simple WYSIWYG pages, to advanced types such as admin user built forms, and shopping categories via Cartridge. Many extras included such as blogging, multi-lingual content, user accounts, tagging, ratings, media library, thumbnailing, and threaded comments. Content can also be edited inline on the site itself. |
Being the most flexible CMS system by providing 1. a CMS for managing a tree of pages and 2. providing the basic building blocks to build your own modules such as blogs, articles etc. and being able to reuse CMS content types.
Short: Customization, reuse, reuse and reuse. |
—
|
—
|
Django page CMS focus on Page hierarchy with rich content. It aims to be a building block that integrate into the admin seamlessly and that you can complement with your own Django applications.
|
django-widgy is a heterogeneous tree editor for Django that is well-suited for use as a CMS. A heterogeneous tree is a tree where each node can be a different type—just like HTML. Widgy provides the representation for heterogeneous trees as well as an interactive JavaScript editor for them. Widgy supports Django 1.4+.
Widgy was originally created for powerful content management, but it can have many different uses. It provides optional integration with Mezzanine using widgy_mezzanine. |
Django Fiber is a simple, open-source, user-friendly CMS for all your django projects. It complements your project, it doesn't take it over.
It allows you to create simple textual, template based pages, add simple content items in pages and views, and adds simple menus that always work. All this can be maintained using a friendly frontend admin interface. |
—
|
|
Multi-Tenant
|
|
|
|
django.contrib.sites is supported
|
—
|
—
|
|
—
|
—
|
—
|
|
Python 3 compatibility
|
Currently supports 3.3, 3.4 and 3.5
|
Supports all Python versions Django supports
|
Python 2.7 to 3.4
|
Python 3.2
+ Python 3.3 |
—
|
—
|
|
—
|
—
|
—
|
|
Django 1.7 Support
|
|
|
|
|
—
|
—
|
—
|
waiting on Mezzanine for Django 1.7 support
|
|
—
|
|
Reuse CMS for a custom content type
|
|
—
|
—
|
|
—
|
—
|
—
|
All widgets are implemented this way, see http://docs.wid.gy/en/latest/tutorials/first-widget.html and http://docs.wid.gy/en/latest/tutorials/proxy-widget.html
(for page types using widgy_mezzanine, please refer to Mezzanine docs) |
|
—
|
A Django content management system focused on flexibility and user experience
https://janjislot.org/
Wagtail's editing interface is entirely independent of Django Admin / Grappelli. It has been custom designed for optimal user experience, and it is lightweight, responsive, and fast.
Although it will happily power a blog or small website, Wagtail is a compelling choice for large-scale and enterprise projects. It can be used to implement websites of any size, scaling to cope with many thousands of pages (for example http://www.rca.ac.uk, which has over 10,000) and incorporating high end features like native support for automated cache invalidation for frontend caches such as Varnish, Squid, etc.
The easy-to-use and developer-friendly enterprise CMS powered by Django
+ Frontend editing
Case Studies: https://www.django-cms.org/en/case-studies/
CMS framework for Django
Earlier versions date back to Django 1.1
Included page types range from simple WYSIWYG pages, to advanced types such as admin user built forms, and shopping categories via Cartridge.
Many extras included such as blogging, multi-lingual content, user accounts, tagging, ratings, media library, thumbnailing, and threaded comments.
Content can also be edited inline on the site itself.
A Django-based CMS with a focus on extensibility and concise code
1.5.x
1.6.x
1.7.x
Compression: No, should be done in 3rd party app
Short: Customization, reuse, reuse and reuse.
+ Python 3.3
Wagtail + CodeRed Extensions enabling rapid development of marketing-focused websites.
A Django blog app implemented in Wagtail
Official Django page CMS git repository
A CMS framework for Django built on a heterogenous tree editor.
Otherwise, there is a 64 level depth limit on the content of a page from the django-treebeard MP_Node implementation
Widgy was originally created for powerful content management, but it can have many different uses.
It provides optional integration with Mezzanine using widgy_mezzanine.
(for page types using widgy_mezzanine, please refer to Mezzanine docs)
Django Fiber - a simple, user-friendly CMS for all your Django projects
It allows you to create simple textual, template based pages, add simple content items in pages and views, and adds simple menus that always work.
All this can be maintained using a friendly frontend admin interface.
feincms3 provides additional building blocks on top of django-content-editor and django-tree-queries which make building a page CMS (and also other types of CMS) simpler.
Showing 10 of 39 packages in this grid.
Features Being Compared
508 compliant?
See http://webaim.org/standards/508/checklist
Demo
Demo site
WYSIWYG Editor
Support for WYSIWYG editor(s) and/or markup formats.
Page Depth
Maximum depth of page hierarchy.
In-line Editing / Frontend-Editing
Support for editing page content in-line (as opposed to only in the Django admin)
Page Sorting
Visual rearranging of page hierarchy (as opposed to entering index numbers)
Plugins
The content of the pages can be easily extended by 3rd-party apps.
Tests
Contains a suite of unit tests.
Pypi Installable
Can be automatically installed with dependency resolution via pip or setuptools.
Documented
Contains thorough documentation.
Multisite
Allows a single installation to serve multiple websites.
Multilingual
Full builtin multilingual support.
SEO
Builtin tools for SEO
Granular Permissions
Is a granular permission system provided?
Revision
Builtin revision controlled content
Tags
Builtin tag support
App Integration
Does the CMS support integration of any Django app which provides at least a urls.py?
Test coverage
The current test coverage of the package in percent.
Django Versions
Which versions of Django are supported?
Multi-device
Can a single instance serve up different templates for different devices? (eg mobile phones)
Moderation Workflow
Allows for complex, enterprise-ready moderation workflows with hierarchical permission levels and previews of unpublished changes.
Media asset merging and compression
Media assets JS/CSS are compressed in production mode, with a minimal effort
Continuous Integration
Does the project have a (public) continuous integration server showing the community it's current build status?
List of Sites
Is there a list of sites online that use the CMS?
Main focus
What is main target use case for the application (blogs, personal pages, web magazines)?
Multi-Tenant
If the CMS supports multiple sites, can they all be hosted from a single running instance of the application?
Python 3 compatibility
Django 1.7 Support
Whether the project also supports Django 1.7.
Reuse CMS for a custom content type
Is it possible to reuse the CMS for a custom content types (different from the Page model itself). Example of such would be a Document model tree having the same management interface as the Page model.