{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "error-404",
  "title": "404 page",
  "description": "A full-page 404 error state with go-back and home recovery actions.",
  "registryDependencies": [
    "button",
    "https://www.quilldesignsystem.com/r/icon.json"
  ],
  "files": [
    {
      "path": "registry/blocks/error-404.tsx",
      "content": "import { Button } from '@/components/ui/button'\nimport { Icon } from '@/components/ui/icon'\n\n/** A full-page 404 error state with go-back and home recovery actions. */\nexport function Error404() {\n  return (\n    <div className=\"flex h-frame-sm w-full flex-col items-center justify-center gap-4 bg-background px-6 text-center text-foreground\">\n      <span className=\"font-heading text-4xl text-muted-foreground\">\n        404\n      </span>\n      <div className=\"flex flex-col gap-1\">\n        <h1 className=\"fraunces-text font-heading text-2xl\">Page not found</h1>\n        <p className=\"max-w-card text-sm text-pretty text-muted-foreground\">\n          The page you’re looking for doesn’t exist or may have been moved.\n        </p>\n      </div>\n      <div className=\"flex gap-2\">\n        <Button variant=\"outline\">\n          <Icon name=\"arrow_back\" /> Go back\n        </Button>\n        <Button>Take me home</Button>\n      </div>\n    </div>\n  )\n}\n",
      "type": "registry:component",
      "target": "components/quill/error-404.tsx"
    }
  ],
  "meta": {
    "intent": [
      "feedback"
    ],
    "use_when": "You need a full-page not-found state with recovery actions.",
    "not_for": "the resource exists but is legitimately empty (no items yet), not missing or misrouted → empty-state; the error is recoverable inline on the current page, not a full-page dead end that needs its own route → alerts"
  },
  "docs": "A full-page 404 error state with go-back and home recovery actions. Do: Offer both a contextual escape (Go back) and an absolute one (Take me home) — never strand the user with only one recovery path. Don't: Leave a 404 page with no action at all, or only a single 'Home' link buried in a header the user has to hunt for. Use empty-state when the resource exists but is legitimately empty (no items yet), not missing or misrouted. Use alerts when the error is recoverable inline on the current page, not a full-page dead end that needs its own route.",
  "categories": [
    "feedback"
  ],
  "type": "registry:block"
}