Resuming Wagtail's UI team
After a long hiatus, we're resuming the UI team and inviting contributors to coordinate adoption of modern design principles and technologies

We’re excited to announce that the Wagtail UI team is back in action! Over the past three years, Wagtail's UI has evolved rapidly. Our goal is to make Wagtail even more intuitive, accessible, and visually appealing for content editors and developers alike.
The UI team will focus on coordinating the adoption of modern design principles and technologies across the project, supporting the items in our roadmap. Here are some ideas for what the team could look into:
- Implementing a headless userbar
- Improving performance
- Lazy-loading UI components and Stimulus controllers
- Acting on performance audit findings
- Switching from Sass to vanilla CSS
- Enhancing message banners and upgrade notifications
- Strengthening QA testing and ATAG compliance
- Improving the mobile UI experience
- Revisiting breakpoints based on modern devices
- Adapting to Tailwind v4 API changes
We’d love your input! If you’re interested in contributing—whether through design, front-end development, or feedback— join the #ui channel on our Slack to collaborate.