-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[examples] Swap Next.js examples between App Router and Pages Router; update naming convention #38204
[examples] Swap Next.js examples between App Router and Pages Router; update naming convention #38204
Conversation
I pushed a change who renames more examples, while we are at it:
|
Good call @oliviertassinari ! I just added notes to the |
Signed-off-by: Olivier Tassinari <[email protected]>
We will need to cherry-pick this to production as soon as merged, otherwise, all the links will be broken. |
@samuelsycamore @oliviertassinari I just released v5.14.3. Let me know how we should proceed about this regarding merging this PR and cherry-picking it to production. |
I think we'll have to rely on @oliviertassinari - I'm not sure how to pull this off myself. 😅 |
@DiegoAndai I think that you can merge and follow https://github.com/mui/material-ui/blob/master/scripts/README.md#deploy-documentation-without-a-release, it's up to date. |
@samuelsycamore After merging, I think that we could:
|
Alright, I'll go ahead and merge this while it's still up to date and follow the instructions to deploy without a release, then follow up with further improvements to the Examples page in a new PR. |
… update naming convention (#38204) Signed-off-by: Olivier Tassinari <[email protected]> Co-authored-by: Olivier Tassinari <[email protected]>
Closes #38073; part of #34905.
Going forward, users will expect that new Next.js projects follow the App Router pattern. This PR updates the names of the Next.js examples for all Core libs to make the App Router examples the defaults. We should keep the Pages Router examples for the foreseeable future, but flag them instead.
So
material-next
becomesmaterial-ui-nextjs-pages-router
material-next-app-router
becomesmaterial-ui-nextjs
Preview: https://github.com/mui/material-ui/tree/39f8250b298537f8aa87a3ec525920b1ddb2fcf7/examples
https://deploy-preview-38204--material-ui.netlify.app/material-ui/getting-started/example-projects/