Components, buttons, and links: shared rules for familiar actions
Understand component anatomy, variants, and states, and why buttons and links should follow their actual purpose.
A component is a reusable interface part such as a button, navigation menu, or field. Shared components make familiar actions look and behave similarly so customers do not need to relearn each page.
A component is more than an appearance. The design system also explains its parts, suitable uses, and behavior before and after interaction.
Anatomy, variants, and states
Consider an inquiry button:
| Concept | What it describes | Example |
|---|---|---|
| Anatomy | The component’s parts | Label, background, boundary, and an optional icon |
| Variant | A different purpose or size within the same component | Primary action, secondary action, or size option |
| State | What is happening now | Available, keyboard-focused, sending, or unavailable |
Changing a label does not require a new button variant. States also need more than color changes: sending should communicate progress, and unavailable actions may need an explanation nearby.
Choose buttons and links by behavior
A link takes someone to a page, file, or location. A button performs an action such as submitting a form, expanding a menu, or closing a dialog. A link can have a prominent button appearance while retaining the correct underlying role.
Use wording such as “Book a consultation” or “View service coverage” to explain the next step. Avoid vague labels such as “Click here.” Where several actions appear together, establish priority. High-impact actions, such as cancelling a confirmed appointment, need clear consequences and suitable confirmation.
Try components with real wording
Replace “Inquire” with a longer label, then switch language and narrow the window. Text should remain readable and the activation area usable. Keyboard users should see their current position, and essential instructions should not depend on hover.
You confirm that wording matches the actual business promise. The team handles structure, sizing, and behavior. Consistent-looking buttons may still lack working functionality. See the form guide for submission outcomes and contrast and target sizes for interaction checks.
Our website design and development service includes the reusable controls needed for the agreed pages. We connect labels, states, and actions to the intended customer task, and review them in the browser.