service-manual 1 linked patterns checked
GOV.UK Service Manual: Building a robust frontend using progressive enhancement
Documents HTML-first services, CSS and JavaScript failure conditions, feature detection, testing on lower-powered devices, preserving core functionality when JavaScript fails, and using other channels only when core functionality cannot be provided without JavaScript.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Graceful degradation | Choose graceful degradation when users stay on the same surface and the core task continues with fewer capabilities. | The baseline path can complete the same core task or the interface explicitly says why it cannot. | GOV.UK documents baseline HTML, JavaScript failure risks, and preserving core functionality when enhanced layers fail. |
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: Government Digital Service. Last checked: .