Feature request: navigation rail

Open
#19,387 24 comments 30 reactions 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 the linked Material 3 navigation rail overview, including its responsive design section, and compare the requirements with the existing Material UI navigation components. Define the component’s scope, behavior for 3 to 7 destinations, responsive interactions, and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Description

design: material scope: new proposal type: new feature

New material component, the navigation rail.

  • good for 3 to 7 destinations
  • part of the navigation design spec... see the responsive design section to see how this mixes in with other navigation components

https://m3.material.io/components/navigation-rail/overview

Benchmarks

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.