Skip to content

Conversation

@edwardhorsford
Copy link
Contributor

@edwardhorsford edwardhorsford commented Dec 23, 2025

Description

Adds example pages for:

  • 404 - Page not found
  • 500 - Something went wrong
  • Service unavailable - planned downtime
  • Service unavailable - unplanned downtime
  • Confirm delete

Content TBC. These are mostly for internal reference and it's unlikely we'll use in UR. The header adapts between them depending on the use case.

References:

404 - Page not found

In most cases we avoid returning a 404 - instead redirecting to the next level up. Eg if a specific clinic can't be found, we redirect to the index of clinics. There's probably some situations where a 404 would be better though.

Screenshot 2025-12-23 at 14 18 06

500 - Something went wrong

To be used in situations where there is some internal failure (api issue?) but the service is otherwise up.

Screenshot 2025-12-23 at 14 18 15

Service unavailable - planned downtime

Note this has the most minimal of navs as it's assumed it will be served statically and separately from our main app.

Screenshot 2025-12-23 at 14 18 40

Service unavailable - unplanned downtime

Used this Register trainee teachers example for unplanned downtime and update message.

Note this has the most minimal of navs as it's assumed it will be served statically and separately from our main app.

Screenshot 2025-12-23 at 14 18 56

Confirm delete

This mostly replicates the existing page from production.

Screenshot 2025-12-23 at 14 19 12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant