[RFC] Links vs Buttons

Open
#23,444 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, react
Domain
design, frontend

Research direction

Start by reading issue #22780 and the existing links-versus-buttons discussion. Compare the visual treatment in the navigation and documentation, then define a single consistent stance; the work is done when the decision and its application across the referenced docs are clear.

Written by the indexing model from the issue text.

Description

discussion docs RFC scope: button scope: link umbrella

Opening this to be filled with arguments why or why not buttons should look like anchors.

We accidentally merged a change that enforced the distinction partially. Any decision we do make should be applied consistently. The button vs anchor discussion is already hard to follow. We shouldn't make it more complicated by applying different stances throughout our docs.

#22780 enforced different visuals for links in the nav menu but didn't make a proper argument why.

Dominant language
JavaScript
Stars
99.1k
Forks
32.5k
Avg merge
2d 17h
Merged PRs (30d)
106

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mui/material-ui

All issues in mui/material-ui

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.