404 Not Found Page #559
Open
404 Not Found Page #559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@codeaashu Kindly review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR introduces a custom 404 Not Found Page along with a default route for the application. The 404 Not Found Page displays a visually appealing background, a prominent "Page Not Found" message, and a button that redirects users to the homepage when clicked. The default route ensures that all non-matching routes will be handled by this 404 page.
Related Issues
Resolves #558
Changes Proposed
NotFoundPage Component: A React component was added for the 404 page. It includes:
-A background image.
-A "Page Not Found" message.
-A "Go to Home" button that redirects the user to the homepage.
Routing Updates:
A default route (*) has been added to handle all non-existent routes, displaying the NotFoundPage for any unmatched URL.
The previous default route for the homepage ("/") remains intact, and now it redirects users from invalid paths to the 404 page.
Checklist
Screenshots
Note to reviewers