We’ve talked before about the GOV.UK Design System and how we’ve worked to make everything it contains accessible, easy to implement and of a high quality.
Similarly, a component or pattern - however accessible, robust, well-researched and reliable it may be - is only as good as the guidance that explains how to use it.
Even when the GOV.UK Design System was still a prototype, we knew that providing clear documentation to support the things it contained was central to its success.
We spoke to people from a broad range of disciplines to get a balanced view - from those who work directly with user interfaces like designers and frontend developers, to those in decision-making roles, like product managers and business analysts.
We asked users what information they’d need in order to trust a component or a pattern enough to use it and used their feedback to refine our approach into what we have today.
For this reason, all components and patterns in the Design System follow a content pattern which explains, in the following order: