User Story: Error Pages

[DarrachBarneveld]

As a User, I can see error pages (such as 400, 403, 404, 500) so that I am informed and guided appropriately when unexpected issues arise during my interaction with the website.

Acceptance Criteria:

• When encountering a 400 error page, I should be notified that there was a bad request and provided with instructions or a link to navigate back to a functional page.
• Upon encountering a 403 error page, I should be informed that I do not have permission to access the requested resource..
• When encountering a 404 error page, I should be informed that the requested page or resource does not exist and guided to relevant sections of the website or provided with a search option.
• In the event of a 500 error page, I should be notified that there was an internal server error and prompted to try again later.
• All error pages have navigation buttons to return home

Tasks

• [x] Implement custom error pages for 400, 403, 404, and 500 errors.
• [x] Ensure error pages provide clear and concise messaging to users.
• [x] Verify that error pages include relevant links or instructions for users to navigate back or seek assistance.
• [x] Test error pages to confirm they display correctly and function as intended in various scenarios.

[DarrachBarneveld]

All error pages created, highlighting the reason for error and the navigation to home page