Button

Button

Buttons allow users to perform an action or to navigate to another page / view. Buttons let users understand what will happen next.

Weight

Reserve bold buttons for primary/important actions on a page or in a view. Subtle buttons should make up most of the interface, while a weight of "none" should be spared for subordinate actions.

Tone

• active (default)
• critical - not to be used when weight is "none"
• passive - only to be used when weight is "none"

Active is the default tone, use this to let user know there's an action they can perform to go to a new view or go to the next step in the flow.

Use the critical tone when an action has potentially destructive effects on the user's data (delete, remove, etc). If using the critical tone button as a standalone, we recommend styling it as a subtle button. Within a set, the danger button should be styled as a bold button.

Passive tone can only ever be used when weight is "none". Always use this next to other buttons and never use it as standalone button.

Icons

Icons can be used in buttons when additional clarity is required and the icon is highly relevant to the action. Avoid using two icons in a button.

Use iconBefore to help the user learn about the action of the button quickly or to indicate the user will go back to previous step in the flow.

Use iconAfter to help the user learn if there is a change in the flow (open new tab or window for example) or to indicate the user will go to next step in the flow.

ActionButton

Action buttons allow users to perform an action. They're used for similar, task-based options within a workflow, and are ideal for interfaces where buttons aren't meant to draw a lot of attention.

Weight

Where two or more actions are available you may want to emphasise one action over others. Use the subtle weight variant to drop the border.