This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.
Sub teams supplement the Wagtail core team with more diverse teams focused on specific areas, each led by a member of the core team.
Want to know more? Read on Announcing Wagtail sub teams
Here are our currently active sub teams:
Accessibility
The accessibility team focuses on improvements to the accessibility of Wagtail, and of websites built with Wagtail. Everyone is welcome regardless of skill level or background. Find us on the Wagtail Slack in #accessibility.
Documentation
Documentation is a crucial part of the Wagtail open source project. It helps people get started, and explains how to use Wagtail. Improving the documentation is the mission of the documentation team.
Some long term goals are:
- Reorganise the documentation into clear sections.
- Move the user guide into a separate project.
- Start supporting translations. Please join the Documentation team. #documentation on Slack.
Performance
This team will focus on measurement and optimisation of both backend (admin, API and template responses) and front-end, with the goal of demonstrably improved performance on each release.
Please join the #performance-working-group team on Slack.
Security
UI
The UI team is cross-functional, with designers, UX, developers involved. We look after the CMS user interface and the maintainability of Wagtail’s UI architecture. Find us on the Wagtail Slack in #ui.
Packaging
DRAFT: Packaging Team
Developer relations
The developer relations team oversees how we engage with our community of developers. Everyone is welcome regardless of skill level or background. Find us on the Wagtail Slack in #developer-relations.