Where to go next¶
The tutorial is over. You can publish CMS pages, write your own plugins, and mount Django apps via apphooks. This page is a map of where to look when you need more.
If you have a task in mind¶
Reach for How-to guides. The how-to guides are short, focused recipes:
How to manage caching — page and plugin caching.
How to serve multiple languages — serve content in multiple languages.
Multi-Site Installation — run multiple sites from one project.
How to extend the Toolbar — add custom buttons and menus to the toolbar.
How to implement content creation wizards — create content-creation wizards for the toolbar’s Create button.
How to extend Page & PageContent models — add custom fields to pages.
How to run django CMS in headless mode — use django CMS as a headless backend.
Install django CMS with Docker and Install django CMS manually — deployment-shaped setups.
If you want to understand why¶
Reach for Explanation:
Philosophy — design principles behind the CMS.
Plugins — the model/view/template split for plugins, and how plugins compose with placeholders.
Application hooks (“apphooks”) — what an apphook really is.
Publishing — drafts, versions, and the publishing model.
Permissions — the permission system.
Three topics worth exploring next¶
Most production sites need at least these three things. None of them are part of django CMS core, but each has an official package and a how-to.
Versioning. The core publishing flow has draft/published states. For richer editorial workflows (multiple draft versions, scheduled publishing) add djangocms-versioning.
A rich-text editor that suits your team. The CMS works with several editors; pick one and install it as a frontend integration. See Some commonly-used plugins.
A frontend admin you’re happy with. djangocms-simple-admin-style
provides a polished admin skin that pairs with the toolbar. The
quickstart project includes it; you can adopt it in a manual install
too.
Community¶
The friendliest place to ask questions is the django CMS Discord server.
If you find a bug, file it on GitHub. If you want to help, see Contribute — documentation fixes are some of the most valuable contributions and one of the easiest places to start.