Question page
Button group
Display multiple related actions stacked or in a horizontal row to help with arrangement and spacing.
Props
alignment
GoabButtonGroupAlignment
Positions the button group in the page layout.
gap
GoabButtonGroupGap
Sets the spacing between buttons in the button group.
Defaults to
relaxed.
testId
string
Sets a data-testid attribute for automated testing.
mt, mr, mb, ml
Spacing
Apply margin to the top, right, bottom, and/or left of the component.
Button with Icon
Disabled button with a required field
Reset date picker field
Show a label on an icon only button
Other
Tip
Use Block for general layout and spacing. Use ButtonGroup for semantically related action buttons.
Sizing
Don't
Don't use different button sizes in the same area to emphasize hierarchy.
Don't
Don't stack standard and full width buttons.
Do
Use full width buttons on mobile.
Tip
Match gap to button size. Use 'relaxed' gap with normal-sized buttons and 'compact' gap with compact buttons.
Positioning
Don't
Don't group more than 3 actions together. Consider using an overflow menu for additional options.
Do
Use a button group when putting multiple buttons together.
Tip
Use 'end' alignment for modal action buttons so they sit at the bottom right, following the natural reading flow.
Types
Button types
- Primary - If there is only one button on a page, it should be a primary button. For citizen facing applications, generally there should only be one primary button on a page.
- Secondary - Use secondary buttons for less important actions on a page. Often paired with a primary action as a secondary action.
- Tertiary - Use tertiary buttons for links that should function like a button, such as “edit” or “cancel” in applications. It’s okay to use more than one tertiary button on a page.
Do
Use a primary button for main actions and a secondary button for less important actions.
