Hover Card

Use HoverCard to build consistent, accessible interfaces aligned with the shared design system.

Installation

1. Copy the source code:

• Source in this monorepo: packages/ui/src/components/hover-card.tsx
• Place in your project: components/ui/hover-card.tsx
• Required utility: lib/utils.ts (for cn helper)

2. Update the import paths to match your project structure.

Usage

import { Button } from "@hoag/ui/components/button";
import {
  HoverCard,
  HoverCardContent,
  HoverCardTrigger,
} from "@hoag/ui/components/hover-card";
 
export default function Demo() {
  return (
    <HoverCard>
      <HoverCardTrigger asChild>
        <Button variant="link">@hoag-ui</Button>
      </HoverCardTrigger>
      <HoverCardContent className="w-80">
        Build composable components for docs and products.
      </HoverCardContent>
    </HoverCard>
  );
}

Import

import {
  HoverCard,
  HoverCardContent,
  HoverCardTrigger,
} from "@hoag/ui/components/hover-card";

Basic Example

import { Button } from "@hoag/ui/components/button";
import {
  HoverCard,
  HoverCardContent,
  HoverCardTrigger,
} from "@hoag/ui/components/hover-card";
 
export function HoverCardBasicExample() {
  return (
    <HoverCard>
      <HoverCardTrigger asChild>
        <Button variant="link">@hoag-ui</Button>
      </HoverCardTrigger>
      <HoverCardContent className="w-80">
        Build composable components for docs and products.
      </HoverCardContent>
    </HoverCard>
  );
}

Accessibility Checklist

• Verify semantic roles and ARIA attributes for interactive behavior.
• Keep keyboard navigation and focus visibility consistent in all states.
• Ensure color contrast meets accessibility requirements in light and dark themes.
• Provide screen reader context for dynamic state or content changes.

Testing Checklist

• Add render tests for default and key variant states.
• Add interaction tests for callbacks and state transitions.
• Add visual regression checks for responsive and theme variations.
• Cover edge states such as loading, empty, disabled, and error.

Production Tips

• Wrap component logic in feature-level abstractions for domain behavior.
• Keep visual variants centralized to avoid style drift across screens.
• Reuse a single import path strategy for simpler refactors.
• Mirror documented states in Storybook and QA checklists.

Named Exports

• HoverCard
• HoverCardContent
• HoverCardTrigger

API Reference

For authoritative prop signatures and implementation details, inspect:

• packages/ui/src/components/hover-card.tsx