Component: Cards

Summary

Cards are a common design pattern used in digital interfaces to present related content in a structured, visually appealing way.

They help users quickly scan and interact with information while maintaining a clean and organized layout. Whether used in dashboards, product listings, or social media feeds, cards enhance user experience by offering a flexible and consistent way to display content.

What's a Card?

A card is a component that groups related information into a contained layout, visually resembling a playing card. Each card serves as a self-contained unit that presents a summary of information and often provides a link or action for further interaction. Cards are designed to be modular and responsive, making them ideal for different screen sizes and user contexts.

  • Container: The outer boundary that defines the card’s space.

  • Header Text: The card title, usually a key identifier of the content.

  • Brow Text: Metadata such as author name, date, or category. (Available on Trial Court and the Supreme Court design instance)

  • Media: Images, videos, or other visual elements that enhance content presentation.

  • Supporting Text: A brief description or summary.

  • Buttons or Links: Calls to action (CTAs) such as “Learn More” or “Buy Now.”

  • Icons: Additional interactions, such as sharing, liking, or saving content.

Examples of Cards

Cards can be used to showcase Branch Policies and Administration, or Programs that are offered, etc. 

  • News Websites: Article previews with headlines, images, and brief summaries.

  • Dashboards: Widgets that present key metrics or interactive controls.

Card with a Button

You can also use cards with a button to send the user off to another location. Best practice is to use unique button labels with a hint where it will take the user. 

Card with Links

You can also use links within the cards. 

Image
card graphic

Media (Example 1)

Addition to descriptions, buttons, links within the cards, you can also add images or videos. 

Image
card graphic

Media (Example 2)

Image selected to be on the top. 

Image
body component graphic

Media (Example 3)

Media can be rearranged depending on the desired outcome. You can select for the image to display on the top, left, or right within Media Alignment section. You can only use one card for the left or right alignment within the component.  

Icons (Example 1)

You can also add icons that relate to your content. 

Icons (Example 2)

Another example of icons. 

Benefits of Cards

Cards offer several advantages for both users and designers.

  • Enhance Scannability: Information is presented in digestible chunks, making it easier to scan.

  • Improve Organization: Helps structure content without overwhelming users.

  • Increase Engagement: Clear CTAs and interactive elements encourage user action.

  • Support Responsive Design: Cards adapt well to different screen sizes and orientations.

  • Maintain Visual Consistency: Repeated card patterns create a familiar and user-friendly experience.

Usability Concerns to Consider

While cards offer many benefits, there are potential usability concerns to be mindful of.

  • Overcrowding: Too much content in a single card can make it difficult to read and interact with.

  • Inconsistent Sizing: Uneven card sizes disrupt visual harmony and make scanning harder.

  • Unclear CTAs: If action buttons or links are not clear, users may struggle to understand what to do next.

  • Excessive Scrolling: Poor card layouts can lead to unnecessary scrolling, especially on mobile.

  • Performance Issues: High-resolution images and media-heavy cards can slow downloading times.

When to Use & When to Avoid

When to Use

  • When presenting modular and distinct content (e.g., product listings, news articles, or dashboard widgets).

  • When users need quick access to information without reading long blocks of text.

  • When designing for mobile-first interfaces where flexible, stackable components are beneficial.

  • When requiring consistent, repeatable layouts that improve user familiarity and interaction.

When to Avoid

  • When displaying large amounts of structured data (a table or list might be a better option).

  • When users need to compare multiple items side by side (grids or lists can be more effective).

  • When there is limited screen space, and multiple cards may result in excessive scrolling.

  • When the card design does not support key user tasks or actions, making navigation difficult.

Things to Consider

When designing cards for government services, it’s essential to prioritize clarity, simplicity, and accessibility. Using plain language ensures that services are easily understood by the general public, while clear action buttons help guide users to the next step without confusion. Additionally, visually distinct cards with easy-to-read text, icons, or images make it easier to differentiate categories and improve overall usability.

Accessibility

Ensure cards have proper contrast, readable text, and keyboard-friendly navigation.

Action Clarity

Buttons and links should be clear and easy to interact with.

Plain Language

Use plain language to make information clear and accessible. Avoid jargon, keep sentences concise, and focus on what users need to know at a glance.

User Testing

Regularly test with users to validate the effectiveness of card-based designs.

Resources

Learn More

For an in-depth exploration of button best practices and examples, visit NNg: Best Practices for Card UI Design.

For Developers

Explore Storybook for Inherited CSS Variables and Twig Variables for the card component.