Closed 36degrees closed 7 months ago
In anticipation of moving the Frontend Docs to Netlify, configure Netlify to use our custom error page for 404s.
For example, visiting https://govuk-frontend-docs-preview.netlify.app/foo should display the same GOV.UK branded 404 page as seen at https://frontend.design-system.service.gov.uk/foo.
Leave the existing nginx config for error pages on PaaS, as it's still needed until we've finished the migration.
So that anyone encountering a broken link or attempting to access a non-existent page sees a GOV.UK branded page that reassures them they are on the right site, and directs them somewhere useful.
Developers
What
In anticipation of moving the Frontend Docs to Netlify, configure Netlify to use our custom error page for 404s.
For example, visiting https://govuk-frontend-docs-preview.netlify.app/foo should display the same GOV.UK branded 404 page as seen at https://frontend.design-system.service.gov.uk/foo.
Leave the existing nginx config for error pages on PaaS, as it's still needed until we've finished the migration.
Further reading
Why
So that anyone encountering a broken link or attempting to access a non-existent page sees a GOV.UK branded page that reassures them they are on the right site, and directs them somewhere useful.
Who needs to know about this
Developers
Done when