{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "accordion-disabled",
  "title": "Accordion Disabled",
  "description": "Accordion example: Disabled.",
  "registryDependencies": [
    "accordion"
  ],
  "files": [
    {
      "path": "apps/docs/demos/accordion/disabled.tsx",
      "content": "\"use client\";\n\nimport {\n  Accordion,\n  AccordionHeader,\n  AccordionItem,\n  AccordionPanel,\n  AccordionTrigger,\n} from \"@keystoneui/react/accordion\";\n\nexport default function AccordionDisabled() {\n  return (\n    <Accordion disabled variant=\"box\">\n      <AccordionItem value=\"1\">\n        <AccordionHeader>\n          <AccordionTrigger>What makes our UI different?</AccordionTrigger>\n        </AccordionHeader>\n        <AccordionPanel>\n          Our UI focuses on developer experience and performance.\n        </AccordionPanel>\n      </AccordionItem>\n      <AccordionItem value=\"2\">\n        <AccordionHeader>\n          <AccordionTrigger>\n            How can I customize the components?\n          </AccordionTrigger>\n        </AccordionHeader>\n        <AccordionPanel>\n          Use our CSS variables for global styling, or className and style props\n          for component-specific changes.\n        </AccordionPanel>\n      </AccordionItem>\n      <AccordionItem value=\"3\">\n        <AccordionHeader>\n          <AccordionTrigger>Is it optimized for performance?</AccordionTrigger>\n        </AccordionHeader>\n        <AccordionPanel>\n          Yes, with tree-shaking, code splitting, and minimal runtime overhead.\n        </AccordionPanel>\n      </AccordionItem>\n    </Accordion>\n  );\n}\n",
      "type": "registry:example"
    }
  ],
  "type": "registry:example"
}