Error Page 404
Centered 404 page showing the failed path in mono, three reasons a workspace link goes stale, and search or dashboard as recovery actions.
Centered 404 page showing the failed path in mono, three reasons a workspace link goes stale, and search or dashboard as recovery actions.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Error Page 404 is a full-page centered layout that treats a missing page as information rather than a dead end. The Acme lockup sits above a card that opens with a FileQuestion icon, the heading This page does not exist, and a plain reassurance that the session is fine and nothing else is affected. A muted panel holds the requested path /projects/atlas-q3/settings in mono with a copy button, and a ruled reason list names the three realistic ways a link goes stale inside a product: it was moved or renamed, it was deleted, or you lost access to it. Two buttons give the ways forward, Back to dashboard and Search the workspace.
The requested path is a const and the reasons are a small array, so each has one place to change. The footer explains that a teammate can regenerate the current URL by sharing the page again, turning a broken link into a one message fix.
Reach for this block as the destination for any unresolved route, wired to your not-found handler so the requested path is injected from the actual URL. Point the search and dashboard buttons at your real routes.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the workspace not-found page. Other 404 shapes:
Tip: name the specific reasons a link breaks inside your product; a generic page not found sends the user straight to support.