Buttons are interactive elements that allow the user to perform an action on the page or serve as a prominent hyperlink.
As design trends have evolved over time, it's become more commonplace to style hyperlinks similarly to buttons. This is helpful for creating eye-catching calls-to-action but may encourage button misuse. It's important to know the fundamental difference between buttons and hyperlinks as they are not functionally interchangeable:
While we provide the flexibility for Buttons to function as links, we recommend understanding your particular use cases to make the most informed decision.
Button colors follow our branding theme. We recommend using Buttons for their intended purposes, not to fit a particular application theme.
Primary Buttons serve the purpose of highlighting the most important action a user may take on the current page. When placing Buttons in forms or where users are expected to complete a task, be mindful to set each action at the most appropriate importance level. Actions are displayed from most to least important starting from right to left.
Avoid placing more than one Primary Button within a workflow or page.
Regular Buttons are used most often. They always include a label and may include an icon.
Icon-only Buttons may be used in more condensed layouts. They are typically used to open menus or dropdowns.
Primary Buttons are used for the most important action a user can take on the page, including CTAs and form submission. There should be only one primary per page.
Secondary Buttons are used for lesser important actions. Multiple may be used on a page.
Tertiary Buttons represent the least important action.
Icons are used to give extra visual context to a Button.
By default, they're placed before the label as a leading icon but can be placed after as a trailing icon.
Icons can be either leading or trailing.
Custom icons may be used if the icon does not exist within the Pluma icon library. The sizing will match Pluma's icons. Be aware of how the custom icon's color and style will interact with each Button variant's background color.
Custom icons may be added as a source.
Buttons are available in two sizes: medium and small.
Medium is the default size used in the majority of cases.
Small Buttons are used for smaller screen sizes and less prominent actions on the page.
The base Button uses the primary, secondary, and tertiary colors when no user interaction is detected.
Loading Buttons communicate to the user that some background task is in progress.
On mouse hover, Button styles update to hover colors.
Focused Buttons receive the standard 2px light blue outline.
Button styles update on user activation.
Disabled Buttons cannot be interacted with. Lighter colors are used for all variants.
Danger Buttons receive the critical color treatment to denote destructive actions or errors.
Start labels with a verb. Keep them short and succinct at 1–3 words. Be specific enough that the button is self-explanatory without surrounding context. Use sentence case and no period.
Use the below table for examples of effective label text.
| Type | Pattern | Example |
|---|---|---|
| Primary action | Verb + object | Create campaign |
| Destructive | Delete + object | Delete segment |
| Irreversible | Permanently delete + object | Permanently delete campaign |
| Cancel | Cancel | Cancel |
| Save | Save / Save changes / Save and close | Save changes |
| Progressive | Forward-motion verb | Next, Continue |
| Dialog-triggering | Verb… | Export… |
| Loading state | Present participle… | Saving… |
Add an ellipsis (…) when a button opens a dialog or requires additional input before the action completes. Do not use an ellipsis when the action is immediate, such as navigating to a new page.
Buttons serve as an important starting point for a person to engage with our internal AI agent. Use common questions a person may have about Customer.io as a label to facilitate agent interaction.