Skip to main content
GOV.UK Design System team playbook
Internal
Menu
Team
Roadmap
Sprint board
Table of contents
About these docs
Contribute to the playbook
Who we are
Leadership group
Who we are
What we do
How we work
Leadership charter
What we do
Our products
How we work
Core values
Group norms
Contribution model
View the model
Roles and responsibilities
Delivery cycle
3 week sprint
Reflection week
Guides
How to organise and run a working group review
When to hold a working group review
How to organise a working group review
How to prepare for and run the feedback session
After the working group review has completed
How to purchase something
How to purchase something new
How to renew an existing tool
How to run a Design System team ceremony or workshop
Facilitation principles
Ceremonies
Other team meetings
How to seek approval for travel
How to use GitHub to manage your work
How to create an issue in GitHub
Get help from other roles
A basic template
Product and delivery managers
Designers
Frontend developer
How to be an epic lead
Background info
What is an epic lead?
What an epic lead is responsible for
What an epic lead doesn’t do
Working with the delivery manager and product manager
Using version control (Git and GitHub)
Support branches
Using support branches for previous major versions
Using support branches for hotfixes
Creating a support branch
Making changes to a support branch
Releasing from a support branch
Keeping the changelog on the main branch up to date
Working with Pull Requests (PRs)
Making changes to PRs from external contributors
Reviewing PRs
Merging Pull Requests
Accessibility
Community
Code of conduct for workshops
Delivery management
Design and content
Designers on the team
Development
Using feature flags in GOV.UK Frontend
When a feature flag is useful
When a feature flag is not useful
Types of feature flag
Additional considerations
The lifecycle of a feature flag
Engagement
Product management
Support
Updating the rota
Tell the team
Products we support
Current products
Legacy products
No longer supported
Support channels
Slack
Github
Email
Analysing our support requests
Daily support responsibilities
Daily check in
Communicating with users
Common support responses
Generic responses
Redirects and Not For Team
Latest release questions
Accessibility
Branding
Community Resources
Components
Contributions
Design System Day
Fonts
Mailing list
Meeting requests
Misc
Spam / Security
Website
How to give a new starter access to our support services
Adding to Zendesk
Slack
Technical writing
The ways we work
How tech writers define their skills and work
User research
Weeknotes
Engagement