Usage this month
Resets on the first of next month.
72%
of included API calls consumed
Cards bundle headers, body content, and actions into a predictable surface for dashboards and marketing layouts. Use them in React apps and Next.js pages that need modular content blocks.
Resets on the first of next month.
72%
of included API calls consumed
Outline appearance with tilt animation on hover-capable devices.
Autosaved
Draft content for this preview.
Appearance, size, and rounded radius tokens with a minimal header layout. Code blocks start with Variant: for the row.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Brief supporting description.
Cards are intentionally dumb containers: push business logic up a layer.
Use consistent padding tokens so grids align across breakpoints.
Prefer compound subcomponents instead of one oversized prop bag. Export a small, documented API for your design system.
Keep heading levels coordinated with surrounding page structure for SEO and accessibility.
Keyboard order, focus rings, and ARIA attributes should match production usage. Test with your supported browsers and assistive technologies when semantics are non-trivial.
This preview page exposes a single h1 in the hero for a clean outline.
Colocate examples under the App Router, keep server and client boundaries explicit, and avoid pulling interactive overlays into unexpected server layouts.
Set NEXT_PUBLIC_SITE_URL so canonical and Open Graph URLs resolve on deploy.
Yes. Import it like any other React component; keep interactive subtrees in client components when you need hooks or browser APIs, and leave static structure in server components where possible.
Zentauri UI exposes class-friendly variants and slots so you can extend styles with Tailwind utilities without fighting inline styles.
Primitives follow sensible defaults, but accessibility depends on how you label controls, manage focus, and wire keyboard handlers in your app. Validate critical flows with keyboard-only use and screen readers.