{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "hero",
  "title": "Hero",
  "description": "A centered marketing hero — a release badge, serif headline, supporting copy, and primary/secondary calls to action.",
  "registryDependencies": [
    "badge",
    "button",
    "https://www.quilldesignsystem.com/r/icon.json"
  ],
  "files": [
    {
      "path": "registry/blocks/hero.tsx",
      "content": "import { Button } from '@/components/ui/button'\nimport { Badge } from '@/components/ui/badge'\nimport { Icon } from '@/components/ui/icon'\n\n/** A centered marketing hero — a release badge, serif headline, supporting copy, and primary/secondary calls to action. */\nexport function Hero() {\n  return (\n    <section className=\"flex w-full flex-col items-center gap-6 bg-background px-6 py-20 text-center text-foreground\">\n      <Badge variant=\"secondary\">New — v2.0 is here</Badge>\n      <h1 className=\"max-w-2xl font-[family-name:var(--font-fraunces,Georgia,serif)] text-5xl leading-[1.05]\">\n        The calm design system for building things by hand\n      </h1>\n      <p className=\"max-w-xl text-base text-muted-foreground\">\n        Accessible, themeable components and a single-source token foundation that flows to code\n        and Figma alike.\n      </p>\n      <div className=\"flex flex-wrap items-center justify-center gap-3\">\n        <Button size=\"lg\">\n          Get started <Icon name=\"arrow_forward\" size={18} />\n        </Button>\n        <Button size=\"lg\" variant=\"outline\">\n          <Icon name=\"menu_book\" size={18} /> Read the docs\n        </Button>\n      </div>\n    </section>\n  )\n}\n",
      "type": "registry:component",
      "target": "components/quill/hero.tsx"
    }
  ],
  "meta": {
    "intent": [
      "marketing"
    ],
    "use_when": "You need the top-of-page marketing statement — headline, supporting copy, and calls to action."
  },
  "docs": "A centered marketing hero — a release badge, serif headline, supporting copy, and primary/secondary calls to action. Do: Keep exactly one primary (default-variant) button — the single most important action — with any secondary action as outline/ghost. Don't: Give two calls-to-action equal visual weight; competing primaries dilute the one action that matters most. Use feature-section when you're past the opening statement and need to break down specific product capabilities. Use announcement-banner when the message is a small, dismissible update, not the page's primary opening statement.",
  "categories": [
    "marketing"
  ],
  "type": "registry:block"
}