| Name | Version | Last updated |
|---|---|---|
| dfe-frontend | 2.0.1 | 5 May 2024 |
Use DfE Frontend when your product or service is:
- for internal staff
- provided on the <>.education.gov.uk domain
- provided on <>.service.gov.uk and you want to use components not in the GOV.UK Design System.
If you're in a private beta, and hosting on <>.education.gov.uk, but your public beta and live service will be on <>.service.gov.uk, you do not need to use the DfE header.
Using DfE Frontend to extend GOV Frontend
You cannot use DfE Frontend on it's own, it is not a replacement for GOV.UK Frontend.
Follow the installation instructions for installing DfE Frontend.
Once installed, you can then make use of styles, components, and patterns in the design system.
Why you would use DfE Frontend
There are instances where a component or pattern doesn't exist in the GOV.UK Design System, or, there is a specific use-case scenario which means something specific to DfE is needed.
This is where DfE Frontend comes in. You can use components and patterns from DfE Frontend in your products and services to meet these needs consistently.
If you build something custom, you should contribute it back into the design system for others to use. You can do this by making it available in DfE Frontend.
Working in the open, contributing to common patterns and components, is a requirement of point 13 of the Government Service Standard.
Contributions
DfE Frontend is managed by the DesignOps team and accepts contributions from the design community.
If you are building services and you create custom components or patterns which are not in the GOV.UK Design System, you must contribute these to the DfE Design System in addition you must also contribute back to the GOV.UK Design System backlog as per Service Standard 13 - Use and contribute to open standards, common components and patterns.
You can find guidance for making contributions to DfE Frontend.