Skip to end of banner
Go to start of banner

Cards

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Lead:  Rotem Avidan (Unlicensed) ONGOING


Description

The card is a container of expanded content and actions.

 

Anatomy

The card elements can be changed following the needs, but the base guidelines are:

  1. Keeping elements on hierarchy layout
  2. Action and button will be located on the bottom of the card

  1. Card's body
    The card body can change follow the card mode - read and edit.

    1. Filed / Text
      Using text or filed follow the card status.  

    2. Status icons (optional)
      Status icons may display for more indication. The icons can be toggle or status.

  2. Action bar (optional)
    Cards can include buttons for actionsCards can include buttons for actions

Types

By usage  

An example of a card with no information of the object selected vs. an object with information 


By State 

Unselected
When a card is in the unselected mode, the information will display for the user but not action and edit be working


Selected 
When a card is in the selected mode, the user will be able to edit the value and have action





Usage

Card is a supplementary surface of content and actions for a one selected topic.

The card should be easy to scan and aiming at what action can be done at him.

Card status can be read or edit.

When to use card

Using the card when you have a massive workspace and you need to give more information specific on an item.

Usability guidance

  1. Using components fields clear and understandable what they are aim to.
  2. Highlight action buttons and function in one place.


Structure


Best practices

<<e.g. Slider should display a .label its on>>

????

Accessibility compliance

<<In general each component should be A11y complied,  please follow the 3 guidelines linked below. At the very least we should document that each component is in compliance with each of the 3>>

Focus management

<<How will the component work with keyboard only - without a mouse. Can be reference if written above

We already set a general guidelines described in Keyboard & Focus Management Guidelines >>

Screen reader support 

<<Make sure the components support screen reader for content or behaviour where needed - see Screen Reader Guidelines >>

Contrast & size compliance

<<Visual designers must comply with the minimal of Contrast + Font Size Guidelines for each component>>


Design

Zeplin linkScreen thumbnail
<<Zeplin Link>><<Screen with 200 width>>


Code

<<a box containing the code - discuss with Femi>>




  • No labels