Wagtail at a glance
- Type
- Open-source CMS
- Built with
- Python, on the Django framework
- Hosting
- Self-hosted, or with a specialist Wagtail host or agency
- Best for
- Public sector, universities and charities
Who uses Wagtail
Government departments, health services, universities, charities and publishers use Wagtail, along with companies that already build in Python. It is widely used in the UK public sector.
What Wagtail does well
Free and open source
No licence fees, and the code is yours to change.
Blocks for editors
StreamField gives flexible pages without breaking the design.
Built on Django
Python developers can add anything the site needs.
Built-in essentials
Redirects, search, forms and multi-language page trees come with it.
How Wagtail works
A Wagtail site is a tree of pages, and each page type has its own fields. StreamField lets editors build a page from blocks, such as text, images, quotes and embeds. Images keep a focal point for cropping, documents and snippets are kept apart from pages, and redirects and a page tree per language are built in.
What a Wagtail migration covers
When the connector is ready, Reloque will scan your Wagtail content first and map each field before anything moves. These are the kinds of content a migration has to account for.
- Pages and page tree
- StreamField blocks
- Images
- Documents
- Snippets
- Redirects
- Translations
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave Wagtail, or to make it their next home.
- Needs Python developersPage types and blocks are defined in code, so changes go through developers.
- Hosting is yoursSomeone has to run and update the server, or pay a host.
- Fewer ready-made add-onsThere are far fewer plugins than for WordPress, so more is built by hand.
Planning a move from Wagtail
A Wagtail move centres on the page types and their StreamField blocks, since they hold most of the content.
- List the page types, their fields and where each sits in the page tree
- Note the StreamField blocks and which page types use them
- Check images, documents and snippets, and where pages use them
- Keep the redirects and translations that are already set up
Where Wagtail content could go
The Wagtail connector is planned, and connectors are built in the order people ask for them. These ten work today, in every direction, and Wagtail will join them both ways.
Moving to Wagtail
Moving to Wagtail means creating page types and blocks in code first, then filling the page tree, images and documents.
Wagtail questions
What is Wagtail?
Wagtail is a free, open-source CMS built on Django, the Python web framework. Developers define the page types in code, and editors get a clean admin for writing and arranging pages.
Who uses Wagtail?
Government departments, health services, universities, charities and publishers use Wagtail, along with companies that already build in Python. It is widely used in the UK public sector.
What content can be migrated to or from Wagtail?
A migration with Wagtail typically covers pages and the page tree, StreamField blocks, images, documents, snippets, redirects and translations. Reloque scans your site first and shows what it found before anything moves.
What should I prepare before a Wagtail migration?
A Wagtail move centres on the page types and their StreamField blocks, since they hold most of the content. Four checks help most: (1) list the page types, their fields and where each sits in the page tree; (2) note the StreamField blocks and which page types use them; (3) check images, documents and snippets, and where pages use them; (4) keep the redirects and translations that are already set up.
Can Reloque migrate Wagtail today?
Not yet. The Wagtail connector is planned, in both directions with every CMS Reloque supports. Reloque moves WordPress, Payload, Strapi, Ghost, Umbraco, Drupal, Contentful, Sanity, Storyblok and Webflow today. Tell us your route when you start a free assessment.