Add better and more helpful error pages
See original GitHub issueThe Explorer should have customized error pages, for example the generic 404 page with links to the most common pages, or when a 500 error happens we should probably catch it and display something a bit friendlier than the default Next.js error page. Next.js has an easy way to add a custom 404 page, and a custom page for 500 errors: https://nextjs.org/docs/advanced-features/custom-error-page
We can also use notFound
in getStaticProps to display a custom 404 page for different types of pages. For example if someone went to /blocks/40000000, we could show a “This block doesn’t exist yet. The newest block is block x.” or something like that.
This functionality should be fairly straightforward to add, and nothing too special is required in terms of design—these error pages can reuse the layout components so that they will still have the nav bar and footer.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (8 by maintainers)
Top GitHub Comments
hey @Astrochamp and @SourishS17 , any updates on the progress of this issue? 😃 if you haven’t finished or got busy with other projects you could always open a draft PR so someone else can pick up where you left off
awesome! great to hear. please let me know if you want any design input or anything! I think you could probably reuse the
<AppLayout>
component on the error page files so that they’ll still have the nav bar and footer included