EEnterUI
DocsComponentsThemesDonation
Get Started
  • Component onboarding
    • Card
    • MetricCard
    • ChartCard
    • Badge
    • StatusIndicator
    • Rating
EnterUIDocsFoundationsSurfaces and IndicatorsCard
FoundationsUpdated 6 May 2026

Card

A structured surface for grouped product content.

Card defines how EnterUI handles a structured surface for grouped product content, including default structure, accessible states, and token-driven styling.

#Default usage

Card anatomy

Compose header, content, and footer only when each region has a job.

Release candidate

Ready for final review.

Stable base
Code
<Card className="docs-preview-card">
  <CardHeader>
    <CardTitle>Release candidate</CardTitle>
    <CardDescription>Ready for final review.</CardDescription>
  </CardHeader>
  <CardContent>
    <Badge variant="success">Stable base</Badge>
  </CardContent>
  <CardFooter>
    <Button size="sm" variant="secondary">Review</Button>
    <Button size="sm">Publish</Button>
  </CardFooter>
</Card>

#Import

Code
import {
  Badge,
  Button,
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@froggdesign/enter-ui-react";

#Patterns

Compact content

Card can also be a simple neutral container.

Use the smallest card anatomy that communicates the content clearly.

#Accessibility

Card renders semantic-neutral div regions. Choose meaningful headings in CardTitle and avoid using cards as buttons unless you compose an accessible interactive element inside.

#API

  • Card, CardHeader, CardContent, and CardFooter extend div props.
  • CardTitle extends heading props.
  • CardDescription extends paragraph props.

#Styling

Every exported component accepts className when it renders an element. EnterUI styles use .eui-* classes and --eui-* variables mapped from FroggDesign theme tokens.

PreviousLink
NextMetricCard

On this page

  1. Default usage
  2. Import
  3. Patterns
  4. Accessibility
  5. API
  6. Styling