Page History
...
| Name | Use Case |
|---|---|
| Header toolbar | Actions that affects all applications and the entire user environment. It sits in the header area. |
| Boardlet toolbar | Actions controling a single boardlet and its content. It is always on the top- right side of the boardlet. |
| Ghost boardlet toolbar | It follows the boardlet toolbar rules with one exeption: The first actionbar has only one “More” icon. |
| Card toolbar | Card-specific actions like “Expand/Collapse” if the card supports expand. All other actions are gouped under a “More” icon. |
| Dialog toolbar | It contains actions related to the [dialog]() and follows boardlet behavior. |
| Table row toolbars | Actions that pertain to a single row of a table. They always control functions of the entire row. |
...
- Tabs only. Tabs are arranged side by side. There is no default number of tabs. Exeptions: Vertical tabs are placed below each other.
- Tabs with buttons. Use this when the boardlet has multilayer content and a content action. If an action exists only in one tab, show it disabled in all other tabs to avoid visual jumping. The number of possible actions is limited to a maximum of two buttons.
- Buttons only. Use this when an action is required in the boardlet. The number of possible actions is limited to a maximum of two buttons.
- Tabs with actionbar. Use this as a secondary display option. It can be used in [kiosk mode]() to control tab rotation and timing.
...
For more information, please go to [Content Actions].
Best practices
Place and alignment
...
Hierachy of Action Buttons
The buttons follow a hierarchical order. It is important that you create a visual hierarchy between the buttons in your user interface. The hirachie moves linearly from right to left.
...
