Wagtail is an open source content management system built on Django, with a strong community and commercial support. It's focused on user experience, and offers precise control for designers and developers.
- A fast, attractive interface for authors
- Complete control over front-end design and structure
- Scales to millions of pages and thousands of editors
- Fast out of the box, cache-friendly when you need it
- Content API for 'headless' sites with de-coupled front-end
- Runs on a Raspberry Pi or a multi-datacenter cloud platform
- StreamField encourages flexible content without compromising structure
- Powerful, integrated search, using Elasticsearch or PostgreSQL
- Excellent support for images and embedded content
- Multi-site and multi-language ready
- Embraces and extends Django
Find out more at wagtail.io.
Wagtail works with Python 3, on any platform.
To get started with Wagtail, run the following in a virtual environment:
pip install wagtail wagtail start mysite cd mysite pip install -r requirements.txt python manage.py migrate python manage.py createsuperuser python manage.py runserver
For detailed installation and setup docs, see docs.wagtail.io.
Who’s using it?
Wagtail is used by NASA, Google, Oxfam, the NHS, Mozilla, MIT, the Red Cross, Salesforce, NBC, BMW, and the US and UK governments. Add your own Wagtail site to madewithwagtail.org.
docs.wagtail.io is the full reference for Wagtail, and includes guides for developers, designers and editors, alongside release notes and our roadmap.
- Django 2.0.x, 2.1.x and 2.2.x
- Python 3.5, 3.6, 3.7 and 3.8
- PostgreSQL, MySQL and SQLite as database backends
Previous versions of Wagtail (1.13 and earlier) additionally supported Python 2.7 and Django 1.x.
There is an active community of Wagtail users and developers responding to questions on Stack Overflow. When posting questions, please read Stack Overflow's advice on how to ask questions and remember to tag your question "wagtail".
For topics and discussions that do not fit Stack Overflow's question and answer format, we have a Slack workspace and a Wagtail Support mailing list. Please respect the time and effort of volunteers by not asking the same question in multiple places.
We maintain a curated list of third party packages, articles and other resources at Awesome Wagtail.
Wagtail is sponsored by Torchbox. If you need help implementing or hosting Wagtail, please contact us: firstname.lastname@example.org. See also madewithwagtail.org/developers/ for expert Wagtail developers around the world.
We take the security of Wagtail, and related packages we maintain, seriously. If you have found a security issue with any of our projects please email us at email@example.com so we can work together to find and patch the issue. We appreciate responsible disclosure with any security related issues, so please contact us first before creating a Github issue.
If you want to send an encrypted email (optional), the public key ID for firstname.lastname@example.org is 0x6ba1e1a86e0f8ce8, and this public key is available from most commonly-used keyservers.
Feature releases of Wagtail are released every three months. Selected releases are designated as Long Term Support (LTS) releases, and will receive maintenance updates for an extended period to address any security and data-loss related issues. For dates of past and upcoming releases and support periods, see Release Schedule.
To try out the latest features before a release, we also create builds from master every night. You can find instructions on how to install the latest nightly release at https://releases.wagtail.io/nightly/index.html
If you're a Python or Django developer, fork the repo and get stuck in! We run a separate group for developers of Wagtail itself at https://groups.google.com/forum/#!forum/wagtail-developers (please note that this is not for support requests).
We also welcome translations for Wagtail's interface. Translation work should be submitted through Transifex.
We thank the following organisations for their services used in Wagtail's development:
BrowserStack provides the project with free access to their live web-based browser testing tool, and automated Selenium cloud testing.
Squash provides the project with free test environments for reviewing pull requests.