Roadblock
Introduction#
The Roadblock is a page type used to inform a user that they have met a dead end and cannot continue with their original journey.
Purpose#
- The Roadblock page type is there to present key information to a user when they reach an unexpected end to the task they were trying to complete.
- This can be related to a problem with a service that their task requires - these are 400 client side errors or 500 internal server error pages.
- The page should describe to the user what has happened and tell them how to fix it if possible.
Example#
Content guidance#
Use the ns-landmark - lakeside variant to display clear messaging.
The copy must be in plain English, and if possible help the user out of the situation by providing an actionable option.
You should not use:
- Technical jargon like ‘form post error’, ‘unspecified error’ or ‘Severity code 3’
- Humorous, informal language like ‘oops’
- Negative language
If supporting information is needed, consider using ns-lockup or ns-editorial. This should not detract from the original purpose of the page.
Best practice#
| 💚 Do's | 💔 Don'ts |
|---|---|
| Communicate the message in a clear and concise way as possible | Use the subheading |
| Suggest a next step the customer could take e.g. direct them to webchat or a phone number | Use as errors that are specific to ui elements (such as form fields) or parts of a page (See ns-highlighter ) |
Use for global messaging (See ns-skyline ) |
Principles to follow#
| Creative | Tone of voice | Keywords |
|---|---|---|
| Modern and dynamic | Be active, Be natural | Promotional, Informative |
Feedback#
- Do you have insights or concerns to share? You can raise an issue via Github bugs.
- See all the issues already raised via Github issues.
💩 🎉 🦄 If you have any questions, contact us on Microsoft Teams in the Nucleus Design System channels.