Wagtail CMS’ cover photo
Wagtail CMS

Wagtail CMS

Technology, Information and Internet

A leading open-source CMS powering thousands of organisations worldwide, including NASA, Google, and the British NHS.

About us

Wagtail is built in Python, one of the most popular global programming languages, and is constantly improving and evolving with regular releases and a public roadmap. With its best-in-class content management tools, configurable workflows, translation and localisation capabilities, powerful search, and more, Wagtail is an excellent choice for organisations looking for an enterprise-level CMS. Wagtail is one of the best choices for accessibility, working towards compliance with Section 508, WCAG 2.1 (AA level), and ATAG 2.0 (AA level) standards. Wagtail's powerful API enables content to be centrally managed and published to multiple endpoints to create omni-channel experiences and seamlessly integrates with third-party tools such as CRMs, marketing automation platforms, ticketing, event and payment fulfillment systems. Keep up to date with all new Wagtail CMS news and features by signing up to This Week in Wagtail: https://bit.ly/this-week-in-wagtail

Website
wagtail.org
Industry
Technology, Information and Internet
Company size
51-200 employees
Headquarters
Bristol
Type
Nonprofit
Founded
2014

Locations

Employees at Wagtail CMS

Updates

  • 🌟 It's back! What's New in Wagtail — Register Today! The Wagtail core team is running a free live event to showcase everything that's landed in the 7.3 and 7.4 releases — plus a peek at some exciting things still to come. What's on the agenda? ✅ Autosave — background saving is here at last. No more lost work. ✅ StreamField block settings — a much cleaner, more focused editor ✅ Editor UX upgrades — customizable page explorer & reorderable snippets ✅ Content Quality Checker plus a first look at future Wagtail AI designs ✅ AI-ready docs powered by the llms.txt proposal ✅ Wagtail Space 2026 events and announcements Choose the session that works for you: 📅 Session 1: Tuesday, 19 May @ 17:00 BST 📅 Session 2: Wednesday, 20 May @ 10:00 BST Content editors, developers, product owners — this event was made for you. 👉 Register now using the link in the comments! #Wagtail #OpenSource #CMS #Python #Django #WebDevelopment

    • A Wagtail bird next to text that says What's New in Wagtail CMS? May 2026 19th at 17:00 BST, 20th at 10:00 BST. Join us on Zoom!
  • The new Firefox.com is powered by Wagtail! 🙌 Who says birds and foxes can't get along? 🐦 🦊 😆

    I've been excited to share this post for a while. Check out the new Firefox.com! Mozilla has been such a pleasure to work with to bring this project to life. I'm excited to continue making progress on this over the coming months, as we help migrate more static content into the new multilingual Wagtail CMS backend. And, an extra hat-tip to the team that made it happen: Luciano Ratamero, Mariana Bedran Lesche, Dmitriy C., Jo Sprague. Check out the case study here: https://lnkd.in/g6etY3ud

  • 🚀 What's New in Wagtail is returning — Register Now! The Wagtail core team is hosting a free live event to walk you through everything new in the 7.3 and 7.4 releases — and give you a glimpse of what's coming next. Here's what's on the agenda: ✅ Autosave — background saving is finally here. No more lost drafts. ✅ StreamField block settings — a cleaner, less cluttered editor experience ✅ Editor UX upgrades — customisable page explorer & reorderable snippets ✅ Content Quality Checker and a first look at future Wagtail AI designs ✅ AI-ready docs via the llms.txt proposal ✅ Wagtail Space 2026 events Two sessions to suit your timezone: 📅 Session 1: Tuesday, 19 May @ 17:00 BST 📅 Session 2: Wednesday, 20 May @ 10:00 BST Whether you're a content editor, developer, or product owner — there's something here for you. 👉 Use the link in the comments to register for the time that works best for you! #Wagtail #OpenSource #CMS #Python #Django #WebDevelopment

    • A Wagtail bird next to text that says What's New in Wagtail CMS? May 2026 19th at 17:00 BST, 20th at 10:00 BST. Join us on Zoom!
  • We're EXTENDING our agency survey by two more weeks. If you work at agency that uses Wagtail, we want to connect with you! This brief survey for you to help us find out how we can all support each other better. And we'll be sharing an anonymized report back with everyone who participates. You can find the survey link in the first comment. And in case this post shows up in your LinkedIn feed ages from now, the survey now closes on May 8. #WagtailCMS #Django #Python #OpenSource #Agency

    • A tunnel with a question mark made out of light inside it.
  • If you're considering a #multisite Wagtail set up, this is worth a read!

    View organization page for Torchbox

    9,145 followers

    Managing a whole fleet of websites shouldn't mean doubling your workload, if you get the multi-site approach right. In this blog, Kevin breaks down how Wagtail multi-sites work under the hood, and what to consider before you decide. He explores the clear benefits, like being able to run multiple sites from a single codebase and database, reuse existing page models and components, and launch new sites more quickly without starting from scratch. But like most architectural decisions, the reality of living with a multi-site setup can be more complex. Kev also looks at some of the challenges teams run into over time, including: • Shared codebases becoming harder to manage as complexity grows • Changes made for one site impacting others in unexpected ways • The ongoing overhead of theming and site-specific styling • Governance challenges when teams share the same CMS • Shared dependencies that can’t easily diverge between sites These aren’t reasons to avoid multi-sites altogether, but they do need to be managed deliberately, through clear governance, thoughtful theming approaches, and solid testing across all sites. Multi-sites are a good tool for the right use case. If your sites are closely related and your team understands the trade-offs, they can be a really effective approach. If not, alternatives like separate builds or microsites may be a better fit. If you’re weighing up your options, this is a practical guide to help you make the right call. Read the full blog: https://lnkd.in/e-h-k2Ax Wagtail CMS #WagtailMultiSites

    • A dark-themed blog post banner from Torchbox. The headline reads "Wagtail Multi-sites: A practical guide to getting it right." Below the title, a label reads "Blog | 4 min read." At the bottom, a circular profile photo of the author, Kevin Howbrook, is shown alongside his name and title "Senior Engineer." The Torchbox logo with a flame icon appears in the top right corner. The design features a teal wave graphic in the lower portion.
  • One last tool we want to share with you for #EarthDay this week are Digital carbon ratings. What are they? In short, they are quick letter grades you can use to determine how carbon intensive your website is. We took a look at how Wagtail websites compared to the industry averages and found they did pretty good! We didn't have as many A+ websites as we would like but it's good to see more Wagtail websites were getting As, Bs, and Cs rather than Ds, Es. and Fs. For more on the methods we used, we have a link to the full blog in the first comment. #WagtailCMS #Django #Python #OpenSource #Climate

    • Bar chart: Digital Carbon Ratings: how Wagtail sites score. April 2024 HTTP Archive data, SWDM v4, 2023-2024 Ember grid carbon intensity, 4889 websites. A+: 3.4%. A: 8.9%. B: 16.5%. C: 13.2%%. D: 16.8%. E: 9%. F: 32.2%
  • Thank you 🫶 to everyone who submitted a #GSoC proposal to work with us over the summer! We received 190 proposals and it’s been really tough to narrow it down to the 3-6 we are able to provide mentors for. We’ll hear from Google on confirmed projects next week - looking forward to it!

Similar pages

Browse jobs