Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A card is a container, containing details and actions related to a selected item in the main workspace (e.g. a details panel Details Panel containing cards of events displayed also in the calendar)

...

  • 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 card may also contain:

    • a status bar at the top right side of the card, containing a set of status icons and/or toggle buttons. Toggle buttons will be grouped and aligned left to the status icons outside the status bar.

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

...

  • 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). A card cannot contain a scrollbar.

States

State

Read-Only

Editable

Comment

Regular

Selected

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

Interaction

  • Clicking a card will:

    • Select select that card, deselecting any other cards.

    • If if allowed, switch the card to editable mode.

    • Move move the focus to the corresponding element on the workspace.

  • Clicking a togglebutton on the status bar will toggle between its states (e.g. locked / unlocked).

  • On editable mode, updating any input field will enable both the Save and Cancel buttons. In this case:

    • clicking the Save button will save the data.

    • clicking the Cancel button will roll back the fields to their previous values.

    • clicking either Save or Cancel will also disable both buttons.

  • Clicking the expand Expand button:

    • in read-only mode: will open a popup window with additional information.

    • in editable mode: will open a dialog box with additional settings.

  • Clicking outside the card:

    • Deselects deselects the card (unless the click was on a relevant element on the main workspace).

    • In in editable mode: rolls back to any changes made before clicking the Save button.

Validations & Errors

  • Cards do not require special validations.

  • For validations on card’s content, see Field Validation.

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 users search for a specific item from a list or look for a particular piece of content. In this case, consider using a master-detail design instead

  • when users need to compare attributes from different objects

Future Version (TBD)

collapsibleCollapsible/expandable cardcards.

Accessibility compliance

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

Design

Zeplin link

Screen thumbnail

https://zpl.io/bPkWpRy

...