{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "empty-state",
  "title": "Empty state",
  "description": "A dashed-border empty state with an icon, explanatory text, and a primary action.",
  "registryDependencies": [
    "button",
    "https://www.quilldesignsystem.com/r/icon.json"
  ],
  "files": [
    {
      "path": "registry/blocks/empty-state.tsx",
      "content": "import { Icon } from '@/components/ui/icon'\nimport { Button } from '@/components/ui/button'\n\n/** A dashed-border empty state with an icon, explanatory text, and a primary action. */\nexport function EmptyState() {\n  return (\n    <div className=\"flex w-card-lg flex-col items-center gap-4 rounded-xl border border-dashed border-border bg-card p-10 text-center\">\n      <div className=\"flex size-12 items-center justify-center rounded-full bg-muted text-muted-foreground\">\n        <Icon name=\"folder_open\" className=\"size-icon-2xl\" />\n      </div>\n      <div className=\"flex flex-col gap-1\">\n        <h3 className=\"text-lg font-medium text-foreground\">No projects yet</h3>\n        <p className=\"text-sm text-muted-foreground\">\n          Create your first project and it’ll show up here.\n        </p>\n      </div>\n      <Button>\n        <Icon name=\"add\" /> New project\n      </Button>\n    </div>\n  )\n}\n",
      "type": "registry:component",
      "target": "components/quill/empty-state.tsx"
    }
  ],
  "meta": {
    "intent": [
      "feedback"
    ],
    "use_when": "You need to explain why a view is empty and offer the primary action to fill it.",
    "not_for": "the empty state sits inside an existing surface (a list, a table, a card, a search result) and you compose it from parts: media, title, description and actions. Use empty-state for the finished stand-alone panel → empty; the view is empty because the resource doesn't exist or the route is wrong, not because the user hasn't created anything yet → error-404; there's a multi-step setup to walk through, not a single action to take right now → onboarding"
  },
  "docs": "A dashed-border empty state with an icon, explanatory text, and a primary action. Do: Pair the explanation with a real, primary action button that actually fills the view (e.g. \"New project\"). Don't: Explain that a view is empty and leave the user with no way to act on it from that screen. Use empty when the empty state sits inside an existing surface (a list, a table, a card, a search result) and you compose it from parts: media, title, description and actions. Use empty-state for the finished stand-alone panel. Use error-404 when the view is empty because the resource doesn't exist or the route is wrong, not because the user hasn't created anything yet. Use onboarding when there's a multi-step setup to walk through, not a single action to take right now.",
  "categories": [
    "feedback"
  ],
  "type": "registry:block"
}