Link Button

Overview

Link Button gives a button or link a small, useful moment of feedback: a link earns a small interaction state.

Use it where a CTA needs to feel responsive and intentional, not theatrical. A button should confirm action, state, or direction; it should not become a tiny stage play that delays the click.

The thing to watch is semantics. Keep real button and anchor elements, visible focus, instant activation, and clear loading/disabled states. Motion sits on top of the action; it does not replace it.

Install

Usage

Component Code

Example Production Use Case

Use this as button-interaction implementation guidance. Verify the shipped element semantics, anchor/button mode, disabled and loading states, focus-visible behavior, keyboard activation, and reduced-motion handling before relying on exact props, defaults, imports, or installation steps.

Best Used For

• Secondary actions and navigation links that need a small designed state, not drama.
• Product and docs pages where lightweight feedback supports orientation.
• Link Button adds feedback to an action without weakening semantics, focus, or activation speed.

Not For

Not for destructive actions, unclear states, or places where animation hides the label or delays activation.

Performance Budget

Keep feedback fast, avoid layout-triggering letter movement, and preserve instant activation.

Accessibility and Mobile

Use real buttons or anchors, visible focus-visible styles, and clear loading/disabled states. Touch targets should stay large enough on mobile.

Common Mistakes

• Building Link Button with divs instead of real buttons or links.
• Hiding the label during hover.
• Forgetting loading and disabled states.