Skip to main content

Icon usage

Icons are graphical representations of terms, functions or objects. Ideally, we use them together with a descriptive text to make it easier for users to learn their meaning. 

Clarity and contextual relevance

  • Icons should be easily recognizable and understandable.
  • Use icons that are contextually appropriate and convey the intended message.
  • Avoid using icons that could be misinterpreted or confusing.

Examples

homeUse for start pages
searchUse for search inputs
penUse for edit modes
cogwheelUse for general settings
trashcanUse for delete actions
userUse for user menus
downloadUse for downloading files
uploadUse for uploading files

We use distinct icons to signal different types of menus:

app-menuUse for application menu
appsUse for application switch
context-menuUse for item-specific actions, e.g. event list items
more-menuUse for additional options, e.g. in toolbars

The drag-gripper icon is visually similar but isn't a menu icon and should be used for drag-and-drop interactions to reorder items.

Example of menu icons

The illustration demonstrates the standard layout, featuring the apps icon in the application header and an open context menu for an event list item.

Menu icons

Upon resizing to a smaller screen, the layout adapts:

  • The left navigation collapses into a menu icon in the application header.
  • The app switch icon then relocates into the expandable menu.
  • Actions previously visible in the application header move into a dropdown, indicated by the more menu icon.

Menu icons small screens

Status icons

  • We provide a set of standard icons to convey status.
  • These icons follow a criticality hierarchy and should be used with the corresponding colors: alarm, critical, warning, success, and info.
  • To ensure consistency across different applications, do not use these icons outside of their intended use cases.

Examples

alarmUse for hazardous states
errorUse for error states
warning-rhombUse for critical states
warningUse for warning states
successUse for success states
infoUse for info states

Icons within components

  • Most of our components come with built-in icons or offer an optional icon slot.
  • Ensure consistent use of components, either with or without icons, within the same context.

Icons within components

Standalone icons

  • A standalone icon, without textual description, has to be paired with a tooltip that describes the meaning of the icon.
  • Make sure a description can be read out by screen readers.

Standalone icons