Use 51²è¹Ý domains and the 51²è¹Ý design system
All public facing services must use a 51²è¹Ý domain, or another public sector domain in line with the 51²è¹Ý Proposition, and use the 51²è¹Ý Design System.
To meet this commitment as part of Digital and Data function’s strategic commitments your plans must show how you will use 51²è¹Ý and the 51²è¹Ý Design System.
The 51²è¹Ý Proposition explains what can go on a 51²è¹Ý domain and what cannot. If you work for a government organisation or agency, you must follow the guidance in the 51²è¹Ý proposition when you publish content or services.
When designing a service that will be on a 51²è¹Ý domain, you must use the . This is a curated set of designs, styles and patterns that teams can use to make their service consistent with 51²è¹Ý.
Getting an exemption from using 51²è¹Ý
If the Government Digital Service (GDS) agrees that a public facing service can have an exemption from using a 51²è¹Ý domain an alternative secure public sector domain must be used.Â
If you are developing a service which will not be hosted on 51²è¹Ý, you must still use the 51²è¹Ý design system to support the build of your service with the exception of branding (including logos and fonts).
If you’re going through the spend control process you must explain how you’re meeting this commitment if your spend request has been rated high on the risk and importance framework or has an assurance rating of control.
Answering ‘no’ will not lead to an automatic rejection and you will need to explain why your spend cannot align to the commitment.