Quick links
Standards FAQ
🔑 Sign in
🆕 Create account
💬 Chat on Slack
📩 [email protected]
🖥 Website standards.site
🐦 Twitter @standards_site
📷 Instagram @standards.site
Design & Editing
Editor overview
Preparing logo assets
Click & Hover Behaviors
Text
Media
Accessibility
Button
Dropdown
Sequence
Navigation Menu
Links
Color
Components
Automations
Tooltips
Files & Downloads
Collaborative editing
Project backups
Localization
Workspace & Project Management
Publish & share
Dashboard overview
Workspaces
Workspace members
Viewers
Project access page
Project folders
Project settings
Agency client workflow
Project transfers
Connect a custom domain
SAML SSO integration
Analytics & view history
Your account
Sign in
Plan & Billing
Updating account
Approvals
Button elements are well suited to be Components because they’re simple, occur frequently in a design project, and often use consistent styling. Let’s explore how Components can be used to style buttons.

One common design pattern is having two main button styles: a primary button type for important actions, and a secondary button for less important actions. In this example, we have both of these styles saved as Components.


With Components defined, we can efficiently manage the design of all the Button elements in our project, and ensure they’re referencing the intended design. We can easily make changes to our Components and update all the buttons at once. We can also easily swap between the Primary and Secondary button styles in-context as we work through the design process.
Next
Component use case: Section divider
Back