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 36 Next »

Lead:  Rotem Avidan (Unlicensed) - DONE


Description

A card is an container, appearing in the details panel, containing details and actions related to a selected item in the main workspace

Usage & Behavior

  • A card may appear when selecting an element in the main workspace, e.g. a row or a cell in table

  • When clicked on, some elements may display more than one card, for example, when showing multiple schedule items of a single employee

General guidelines

Structure

  • A card can have two modes: read only and editable

  • On read-only mode the card contains a non-editable text area.

  • On editable mode, the card contains:

    • a set of input fields (e.g. drop-down menus, date pickers, time pickers etc.).

    • an action bar at the bottom-left side of the card (optional). The action bar appears only when a card has been selected.

    • a Save and a Cancel buttons at the bottom-right side of the card.

  • A card may also contain:

    • a status bar at the top right side of the card, containing a set of icons and/or icon buttons.

    • an expand button at the bottom-left side of the card, allowing the user to see more information (see below)

A card in read-only mode

A card in editable mode

Placement & Positioning

  • Cards are aligned to the top and the center of the details panel.

  • Cards have a fixed width. Their height may vary according to the content they hold (a card will not contain a scroll bar)

States

State

Regular

Selected

Comment

Empty state

 

Read-Only

The selected card can be read-only or editable depending on the user’s permissions.

Editable

Editable cards contain actions button, whereas read-only card do not.

Interaction

  • A card must be selected before any editing can be made. A card can be selected in two different ways:

    • Selecting an item from the workspace will open the Details Panel with the corresponding card selected.

    • If the Details Panel is pinned (always open), the cards will be visible, allowing the user to select a card by clicking it

  • Selecting a card moves the focus to the corresponding element on the workspace

Validations & Errors

  • The card itself does not have any associated validations or errors. However, the item content (text field) may have.

  • If another item is selected on the screen, the currently selected card should be closed without saving any changes. closed?

Best practices

  • A card should:

    • contain information relating to one selected item or topic only.

    • be easy to scan.

    • prioritise any actions which can be performed on the item.

  • A card’s content and action options should be clear and understandable.

Use cards

  • when it is beneficial to display extra information alongside the selected item in the workspace.

  • to group several related pieces of information together, providing an entry point for further details on each item.

Don’t use cards

  • When there is a lot of information to display. In this case, use a Popover.s

Future Version (TBD)

  • collapsible/expandable card

Accessibility compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility

Design

Zeplin link

Screen thumbnail

https://zpl.io/bPkWpRy

Code

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


  • No labels