asyncapi
[FEATURE] Enhance 404 Error Page with Search Integration and Quick Navigation Links
Why do we need this improvement?
When users land on a 404 page, they've hit a dead end. Currently, our 404 page shows a simple "page not found" message with just a "Return to Home" button. While functional, it doesn't really help users find what they were actually looking for.
How will this change help?
I think we can do better! A well-designed 404 page can turn a frustrating experience into a helpful one by giving users multiple ways to get back on track.
Screenshots
How could it be implemented/designed?
Search Integration - Add the existing Algolia search button so users can immediately search for what they were looking for. We already have this component SearchButton from AlgoliaSearch.tsx, so it's just a matter of integrating it.
Quick Navigation Links - Provide shortcuts to the most commonly needed sections: Home, Documentation, Tutorials , Tools Better UX Copy - Update the messaging to be more helpful and guide users toward a solution rather than just stating the problem.
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
- [x] I checked and didn't find a similar issue
🏢 Have you read the Contributing Guidelines?
- [x] I have read the Contributing Guidelines
Are you willing to work on this issue?
Yes I am willing to submit a PR!
changes look great but i think there’s no need for this because we already have access to this in the navbar
@vishvamsinh28 That's a fair point about the navbar having these options. However, I'd like to share a few considerations When users land on a 404 ,having recovery options directly in their line of sight (center of the page) reduces cognitive load — they don't have to "hunt" for the navbar to figure out what to do next. On a 404, the most helpful thing we can do is let users search for what they were looking for. Highlighting the search prominently (not just in the navbar) makes it the obvious next step. On mobile, the navbar is typically collapsed into a hamburger menu. A user hitting a 404 on mobile would need to: realize they're lost → open the menu → find search/nav. Putting it on the page itself saves those extra steps.
That said, I totally understand if you feel the current page is sufficient! Just wanted to share the reasoning behind the suggestion. Let me know what you think!
hey @debasish5452v pls keep a tab on the issue itself , its mentioned weather the person who raised it will work on it or not
Thanks for bringing this up @sammy200-ui but I feel like this is a redundant feature.
