{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "accordion-15",
  "type": "registry:component",
  "title": "Accordion 15",
  "description": "Accordion 15. A vertically stacked set of interactive headings that each reveal a section of content.",
  "dependencies": [
    "@radix-ui/react-accordion",
    "lucide-react"
  ],
  "registryDependencies": [
    "accordion",
    "collapsible"
  ],
  "files": [
    {
      "path": "components/watermelon/accordion-15.tsx",
      "type": "registry:component",
      "content": "import type { ComponentType } from 'react'\nimport { ChevronDownIcon, ChevronUpIcon, ClipboardCheckIcon, FolderKanbanIcon, LifeBuoyIcon } from 'lucide-react'\n\nimport * as AccordionPrimitive from '@radix-ui/react-accordion'\n\nimport { Accordion, AccordionContent, AccordionItem } from '@/components/base-ui/accordion'\nimport { Collapsible, CollapsibleContent, CollapsibleTrigger } from '@/components/base-ui/collapsible'\n\ntype FaqItem = {\n  title: string\n  content: string\n}\n\ntype AccordionCategory = {\n  value: string\n  category: string\n  icon: ComponentType<{ className?: string }>\n  faqs: readonly FaqItem[]\n}\n\nconst items: readonly AccordionCategory[] = [\n  {\n    value: 'item-1',\n    category: 'Project Planning',\n    icon: FolderKanbanIcon,\n    faqs: [\n      {\n        title: 'Why do project timelines slip so often?',\n        content:\n          'Timelines usually drift when dependencies are hidden or ownership is unclear. Planning tools work better when milestones, blockers, and approvals are visible in one place instead of being split across multiple updates.'\n      },\n      {\n        title: 'How detailed should a kickoff plan be?',\n        content:\n          'A kickoff plan should be detailed enough to clarify scope, roles, and handoff points without turning into a long document nobody revisits. The best plans are easy to scan and easy to maintain.'\n      },\n      {\n        title: 'What helps teams prioritize requests better?',\n        content:\n          'Prioritization gets easier when business impact, effort, and urgency are evaluated together. A shared framework prevents every request from feeling equally important.'\n      }\n    ] as const\n  },\n  {\n    value: 'item-2',\n    category: 'Team Operations',\n    icon: ClipboardCheckIcon,\n    faqs: [\n      {\n        title: 'How can recurring processes stay consistent?',\n        content:\n          'Recurring operations are more reliable when the team has clear checklists, known owners, and visible status updates. Small process gaps are easier to catch when the workflow is standardized.'\n      },\n      {\n        title: 'What makes internal handoffs smoother?',\n        content:\n          'Handoffs improve when context is transferred with the work rather than explained later in messages. Teams move faster when next steps, due dates, and open questions are already attached to the task.'\n      },\n      {\n        title: 'How do we reduce follow-up overhead?',\n        content:\n          'Follow-up overhead usually grows when updates are scattered and responsibilities are implied instead of assigned. Better visibility removes the need for repeated status checks.'\n      }\n    ] as const\n  },\n  {\n    value: 'item-3',\n    category: 'Client Support',\n    icon: LifeBuoyIcon,\n    faqs: [\n      {\n        title: 'Why do support conversations lose context?',\n        content:\n          'Context gets lost when history, decisions, and issue details are spread across channels. Support workflows feel stronger when the full thread stays connected to the request.'\n      },\n      {\n        title: 'How can updates feel more proactive?',\n        content:\n          'Clients feel better informed when support teams share progress before being asked. Even short updates reduce uncertainty and make longer resolutions easier to tolerate.'\n      },\n      {\n        title: 'What helps escalations move faster?',\n        content:\n          'Escalations move faster when severity, reproduction details, and ownership are defined upfront. Clear escalation paths prevent issues from bouncing between teams.'\n      }\n    ] as const\n  }\n] as const\n\nconst Accordion15 = () => {\n  return (\n    <Accordion className='w-full rounded-xl border border-border/80' type=\"multiple\" defaultValue={[items[0].value]}>\n      {items.map((item) => {\n        const Icon = item.icon\n\n        return (\n          <AccordionItem\n            key={item.value}\n            value={item.value}\n            className='outline-none first:rounded-t-xl last:rounded-b-xl'\n          >\n            <AccordionPrimitive.Header className='flex'>\n              <AccordionPrimitive.Trigger\n                data-slot='accordion-trigger'\n                className='group/accordion-trigger flex w-full items-center justify-between gap-4 px-5 py-4 text-left text-sm font-medium outline-none transition-all hover:no-underline aria-disabled:pointer-events-none aria-disabled:opacity-50'\n              >\n                <span className='flex items-center gap-3'>\n                  <Icon className='size-4 shrink-0 text-muted-foreground' />\n                  <span>{item.category}</span>\n                </span>\n\n                <span className='relative size-4 shrink-0 text-muted-foreground'>\n                  <ChevronDownIcon className='absolute inset-0 size-4 group-aria-expanded/accordion-trigger:hidden' />\n                  <ChevronUpIcon className='absolute inset-0 hidden size-4 group-aria-expanded/accordion-trigger:block' />\n                </span>\n              </AccordionPrimitive.Trigger>\n            </AccordionPrimitive.Header>\n\n            <AccordionContent className='pb-0'>\n              {item.faqs.map((faq) => (\n                <Collapsible\n                  key={faq.title}\n                  className='border-t border-border/70 px-5 transition-colors has-[button[aria-expanded=true]]:bg-neutral-200/60 dark:has-[button[aria-expanded=true]]:bg-neutral-800'\n                  defaultOpen={faq.title === item.faqs[0]?.title}\n                >\n                  <CollapsibleTrigger className='focus-visible:ring-ring/50 flex w-full items-center gap-3 py-4 text-left text-sm font-medium outline-none hover:no-underline focus-visible:ring-[3px]'>\n                    <ChevronDownIcon className='size-4 shrink-0 text-muted-foreground transition-transform data-[state=open]:rotate-180' />\n                    {faq.title}\n                  </CollapsibleTrigger>\n                  <CollapsibleContent className='overflow-hidden pb-4 pl-7 text-sm leading-6 text-muted-foreground'>\n                    {faq.content}\n                  </CollapsibleContent>\n                </Collapsible>\n              ))}\n            </AccordionContent>\n          </AccordionItem>\n        )\n      })}\n    </Accordion>\n  )\n}\n\nexport default Accordion15\n"
    }
  ]
}
