[docs] Update all demos of the docs to include "use client" when needed
Open
Nobody has claimed this yet.
docs
scope: all components
type: enhancement
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary 💡
The nominal user experience for a developer starting with Material UI is the following:
- Start with an example https://mui.com/material-ui/getting-started/example-projects/
https://analytics.google.com/analytics/web/#/analysis/p353089763/edit/IBVRQAiCT2mrgZwzpg9fFQ
- 28% are going with Next.js App router
- Install it, use the first template.
- Go to https://mui.com/material-ui/react-select/#basic-select copy the first demo
- ❌
So I think we should update all the demos in the docs to have "use client" where needed.
Examples 🌈
Motivation 🔦
Better DX
Benchmarks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the getting-started example-projects page and the basic Select demo, then review the linked Base UI useModal example and other documentation demos for Next.js App Router compatibility. Identify demos that require client components and add the directive where needed; done means the demos work when copied into an App Router project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js, react
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100