[FE-81] Add a custom not-found page

[yusuftomilola]

Overview

There is no not-found.tsx, so unknown URLs render Next's unbranded default.

Tasks

• Add app/not-found.tsx styled with the existing design system, linking back to the dashboard or home depending on auth state.
• Add a scoped not-found.tsx for app/(dashboard)/assets/[id] so a missing asset shows a specific message.
• Call notFound() from dynamic routes when a record does not exist, instead of rendering an empty shell.
• Ensure a real 404 status is returned, not a 200 with 404 content.

Acceptance Criteria

• Unknown URLs render the branded page with a 404 status.
• A non-existent asset ID shows the asset-specific not-found message.

Notes for Contributors

Comment below to be assigned.

[rexx010]

Hi, I’m interested in working on this issue. I’ve worked with Next.js routing and dynamic data-driven pages, so I’d add the branded global and asset-specific not-found.tsx pages, update dynamic routes to call notFound() when records are missing, and verify that unknown URLs and missing assets return a real 404 status while preserving the existing design system.

[rexx010]

Hi, I’m interested in working on this issue. I’ve worked with Next.js routing and dynamic data-driven pages, so I’d add the branded global and asset-specific not-found.tsx pages, update dynamic routes to call notFound() when records are missing, and verify that unknown URLs and missing assets return a real 404 status while preserving the existing design system.

[rexx010]

Hi, I’m interested in working on this issue. I’ve worked with Next.js routing and dynamic data-driven pages, so I’d add the branded global and asset-specific not-found.tsx pages, update dynamic routes to call notFound() when records are missing, and verify that unknown URLs and missing assets return a real 404 status while preserving the existing design system.

[jaymhorsh]

@jaymhorsh has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jaymhorsh to this issue.

[drips-wave]

Congratulations, @jaymhorsh! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @jaymhorsh: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊