Skip to content

Card usage guidelines

Cards are structured containers that group related content and actions together, making information easily digestible and actionable.

  • To display a collection of related items such as products.
  • To organize content into distinct and scannable units on a page.
  • To group a mix of elements including text, media, and actions in a consistent and structured way.
  • For simple lists of items that don’t have multiple content types or elements to display.
  • As a form of primary navigation. For this use link tabs or other navigation solutions instead.

Card title

Card subtitle (optional)

Alice's Adventures in Wonderland (also known as Alice in Wonderland) is an 1865 English children's novel by Lewis Carroll.

The card component functions as a stack with multiple slots for elements to be placed into. This allows cards to be completely customizable for any use case. Cimpress UI provides several pre-built card elements to encourage consistency and efficiency. When possible these elements should be used in the card component, but custom elements can also be added when needed. Any custom elements must follow Cimpress UI design standards.

Cost-based Q3

Last updated: May 3, 2023

Active

CIM_TSHIRT

Cimpress Standard T-Shirt

Cards can be used individually or in collections. When the number of cards is variable, like if the list is depending on user filtering for example, the cards should wrap so that the list is always visually consistent.

  • Cards in a list should have 24px of horizontal and vertical spacing between them.

Title

Keep titles concise and descriptive, accurately reflecting the card’s content. In groups of cards, the titles should be consistent in their contents, and should make it easy for users to distinguish between cards.

Additional text

Write clear and concise body text. For longer descriptions, consider truncating the text and providing a “Read more” link.

Icon buttons

Any icon buttons used in cards should be used for standard actions that are obvious to users. If it’s not clear to users what an icon means, use a text button or a different action instead.

Button labels

Use clear and actionable labels for buttons. Refer to the button documentation for specific guidelines.

When possible, text content within cards should wrap naturally to prevent overflow and maintain readability.