Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
A 404 Not Found page is a crucial component of any website or application to gracefully handle user navigation errors and improve the overall user experience. Currently, when users encounter a non-existent route or page, there is no custom 404 page displayed. This can lead to confusion and a less engaging experience.
Task Details:
Design: Create a visually appealing and responsive 404 Not Found page that aligns with the application's theme and branding.
Content: Include a friendly error message, an illustration or graphic (optional), and a clear call-to-action such as a button to navigate back to the homepage or other relevant pages.
Functionality: Ensure the 404 page is displayed when a user navigates to an undefined or invalid route.
Expected Outcome:
A professional and user-friendly 404 Not Found page that seamlessly integrates into the application, enhances usability
I am SWOC contributor, Kindly assign me this issue
What kind of change does this PR introduce?
Related Issue
Closes #108
How Has This Been Tested?
Screenshots (if applicable):
Checklist:
Additional Information