Card Component Guide

Quick Answer

The Card component is a contained layout surface with header, content, action, and footer slots. Use it when a product team needs support for tasks such as grouping a single object or summary, making repeated content scannable, and separating actions from body content. It should feel predictable for designers, engineers, keyboard users, touch users, and people reading long English or Tamil labels. The component documentation is available at Card documentation.

What Card Solves

Card exists to make information scan quickly while preserving meaning, hierarchy, and state. In a real product, this component is not just a visual style. It defines how teams talk about behavior, state, spacing, and responsibility in review.

For Tamil Design System, the content problem matters as much as the component contract. Labels may be English, Tamil, or bilingual. Text can be longer than the demo version. Users may be on mobile devices, zoomed browsers, or public-service workflows where mistakes are costly. A good Card implementation keeps those realities visible.

The practical value is consistency. Designers get a known pattern. Engineers get a maintained primitive. Reviewers get a checklist for empty states, long content, contrast, semantic labels, and how the component behaves inside dense dashboards. Users get an interface that behaves the same way across forms, dashboards, navigation, and tools.

When to Use Card

• Each item has a title, description, and optional action.
• A list needs repeated visual units.
• Content benefits from a bounded surface.

Good use of Card starts with intent. The component should answer a real product question, not merely fill space. When the purpose is clear, the visual treatment, copy, and interaction states become easier to review.

When to Avoid Card

• The page section itself is being turned into a card.
• Cards are nested inside other cards.
• A table or list would compare information better.

Avoiding the component is sometimes the more mature design decision. If the task needs a different semantic control, a full page, a simpler text explanation, or a more explicit confirmation, choose that pattern instead of forcing Card to do too much.

Anatomy and Behavior

• Card root.
• Header.
• Title.
• Description.
• Action area.
• Content.
• Footer.

Each part of Card should have a job. The root controls structure, the visible label communicates purpose, and the state treatment tells users what is possible now. If one of those responsibilities is missing, the component may still look correct in a screenshot but fail in production.

Behavior should be boring in the best way. Hover, focus, active, selected, disabled, loading, empty, and error states should follow the same interaction language used across Tamil Design System. That consistency helps users predict what will happen before they interact.

Props and Implementation Contract

• ClassName controls spacing and layout.
• Children compose slots.
• Semantic heading level should match page outline.
• Interactive cards need real link or button semantics.

Treat props as a product contract, not as a dumping ground for visual switches. A useful prop changes behavior, semantics, state, or a clearly named visual hierarchy. If teams need custom styling, allow scoped class extension, but keep the default component complete enough to use without local patching.

Implementation should also preserve native browser behavior wherever possible. Native controls, real links, real headings, and real table elements carry accessibility, keyboard, and platform behavior that custom markup often breaks.

State and Variant Strategy

Every Card state should be reviewed before the component is marked ready. Start with the ordinary state, then check focus-visible, active, disabled, selected, loading, empty, and invalid states where they apply. A component that only has a polished default state will usually fail the first time it meets real product data.

For Card, the most important release checks are card represents one thing, heading is clear, and actions are separated. These checks should appear in examples, QA notes, and design review, not only in implementation code.

Variants should stay semantic. When a team asks for another color, size, or layout, ask what user meaning it communicates. If the answer is only visual preference, keep the extension local. If the answer is a repeated product state, promote it into the component contract with clear naming and examples.

Accessibility Requirements

• Do not make the entire card clickable unless the target is clear.
• Keep heading levels logical.
• Ensure actions have accessible labels.
• Avoid hiding focus outlines inside card shadows.

Accessibility for Card should be reviewed before visual polish is considered complete. The component must be reachable, understandable, operable, and recoverable. That means visible focus, meaningful names, correct roles, state communication, and a clear path out of mistakes.

The best accessibility test is not only automated. Use the keyboard. Increase browser zoom. Try a screen reader. Replace short demo labels with real production copy. These checks reveal whether Card survives the conditions users actually bring to the interface.

Responsive and Content Behavior

• Use grid tracks that avoid uneven hanging columns.
• Stack card content when action areas get crowded.
• Keep repeated cards visually consistent.

Stack dense displays, preserve readable labels, and avoid shrinking important status or numeric information below recognition. This is especially important for Tamil DS because translated or bilingual labels can expand quickly. Components should use flexible widths, stable spacing, and wrapping rules that keep content readable instead of compressing it into awkward fragments.

Responsive behavior is not just about screen size. It includes pointer type, zoom, reduced motion, high contrast, and slow network states. Card should remain understandable across all of those conditions.

Implementation Notes

Build Card as a reusable primitive first, then compose product-specific behavior around it. The base component should own structure, accessibility, state classes, and predictable spacing. Product screens can then add data, routing, analytics, and copy without reimplementing the core interaction.

Keep the rendered HTML close to the user's mental model. If the component performs an action, prefer a real button. If it navigates, prefer a real link. If it labels a form control, preserve the label relationship. These choices reduce bugs because the browser already understands common interaction patterns.

For maintainability, document the intended extension points. Teams should know which props are stable, which classes are safe to override, and which behaviors should stay centralized in Tamil Design System. That boundary keeps Card consistent while still allowing real products to move quickly.

Copy and Localization Notes

Card should work with direct English labels, longer Tamil labels, and bilingual product copy. Do not assume the demo text is the longest text the component will ever hold. Public-service products often need precise labels, district names, official terms, and explanatory helper text.

When writing copy for Card, prefer concrete nouns and verbs. Replace vague words like item, value, or action with the thing the user recognizes. If the component includes an icon, the text should still carry the meaning. The icon can reinforce the message, but it should not be the only explanation.

For design review, test Card with real examples from the product domain. If the component only works with short English sample text, it is not ready for Tamil DS documentation or production UI.

Design Review Questions

• Does Card solve the current user task more clearly than a simpler component?
• Are the visible labels specific enough to understand without surrounding explanation?
• Are disabled, selected, active, loading, empty, and error states designed before implementation starts?
• Does the component still work with long English labels, Tamil labels, zoomed text, and narrow mobile screens?
• Can a keyboard user reach, operate, and leave the component without losing context?

These questions help the team review Card as part of a real workflow. They also prevent the most common design-system failure: approving a polished default state while ignoring the states that users actually encounter.

Related Components and Alternatives

Choosing Card should be intentional. If the page section itself is being turned into a card, the right answer may be another primitive, a plain content section, a dedicated page, or a clearer workflow. Component decisions are strongest when the team can explain both why this pattern was selected and why nearby alternatives were rejected.

Use the surrounding interface as the tie-breaker. A dense dashboard may need compact state treatment. A form may need clearer labels and validation. A navigation area may need route awareness. A feedback flow may need stronger recovery language. The same Card primitive can support these contexts, but the implementation should not hide the user's goal.

When a pattern starts accumulating exceptions, pause before adding more props. Repeated exceptions may reveal a new component, while one-off exceptions usually belong in the product layer.

Product Examples

• Dashboard summary.
• Article card.
• Project preview.
• Settings group.
• Profile summary.

Examples are useful because they make the component less abstract. When reviewing a Card implementation, ask which example it resembles. If the answer is unclear, the design may be mixing responsibilities from multiple patterns.

Common Mistakes

• Wrapping every page section in a card.
• Placing one card inside another.
• Using cards for dense comparable data.
• Creating card links with no visible focus state.

Most Card mistakes come from treating the component as decoration rather than interaction design. The fix is usually to improve naming, reduce competing behaviors, expose state clearly, or move the task into a better component.

Production Checklist

• Card represents one thing.
• Heading is clear.
• Actions are separated.
• Layout works with long text.
• Interactive area has focus styling.

Use this checklist as the release gate for Card. If one item fails, the issue is not cosmetic. It affects comprehension, accessibility, maintainability, or user trust.

During handoff, record the chosen variants, edge states, responsive behavior, and content assumptions. That note helps QA compare the implementation against the design instead of reviewing only the default state.