404 Custom Error Page#198
Conversation
|
check @prathimacode-hub |
prathimacode-hub
left a comment
There was a problem hiding this comment.
I was expecting more to this issue... The work done is cool, but it needs something more to assign 'Easy' label. It's not sufficient. @dinesh-2047
|
@prathimacode-hub Thanks for the feedback! For now, it's a good starting point—going from nothing to something is progress. But I’d love to improve it further. What specific changes do you suggest to make it worthy of the 'Easy' label? |
You can come with something as per your skills comfort. I'm keeping it open. But add something that brings more value and weightage to it. @dinesh-2047 |
Screen.Recording.2025-02-26.192740.mp4 |
|
how it is ?? @prathimacode-hub |
|
Could you see this link: https://prathimacode-hub.github.io/Dev-Mint. Though error page is showcased with the message as you had given. Still in the website, it had all the necessary links in header and footer for all the pages. So header and footer should have all options and look like how it is in main page. But only middle message will have difference in the content. @dinesh-2047 |
|
https://github.com/user-attachments/assets/7e1afa87-b203-4e53-b4@prathimacode-hub f-0131b2cff6ec please check @prathimacode-hub |
Screen.Recording.2025-02-26.201758.mp4 |
|
Keep background color for Header and Footer same. @dinesh-2047 |
|
|
prathimacode-hub
left a comment
There was a problem hiding this comment.
Your PR is approved. @dinesh-2047


Related Issue
Added a custom 404 Error Page to enhance user experience when accessing a broken or non-existent URL.
✅ IWOC2025 Participant
✅ Contributor
Closes: #184
Describe the changes you've made
Designed and implemented a custom 404 error page using HTML, CSS, and JavaScript.
Included a futuristic 404 error illustration with a robot and a neon cyberpunk theme.
Styled the page to match the website’s dark UI aesthetic.
Added a "Go Back" button for easy navigation back to the previous page.
Ensured responsiveness for different screen sizes.
Type of change
❌ Bug fix (non-breaking change which fixes an issue)
✅ New feature (non-breaking change which adds functionality)
❌ Code style update (formatting, local variables)
❌ Breaking change (fix or feature that would cause existing functionality to not work as expected)
❌ This change requires a documentation update
How Has This Been Tested?
✅ Verified the page renders correctly on different screen sizes.
✅ Tested the "Go Back" button functionality.
✅ Ensured consistency with the website’s design language.
Checklist:
✅ My code follows the guidelines of this project.
✅ I have performed a self-review of my own code.
✅ I have commented my code, particularly wherever it was hard to understand.
✅ I have made corresponding changes to the documentation.
✅ My changes generate no new warnings.
✅ I have added tests that prove my fix is effective or that my feature works.
✅ Any dependent changes have been merged and published in downstream modules.
Screenshot
