-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
New area for userland migrations #7267
Comments
Can you elaborate more? |
I'm not 100% sure that good idea to put it in learn but idk where we can put that. Maybe a new subsection on about but not really right |
In what regard? Ex do you want to know what "userland migrations" are, or are you wondering about the content for the new website section? |
it'd be kinda nice to include within:
perhaps you've given it more thought too @JakobJingleheimer but i am a big +1 to provide this in as many places people will see it here's some MUI examples inline within relevant docs upgrade posts https://mui.com/material-ui/migration/upgrade-to-v6/#breaking-changes |
Yes! If the codemod is available when the feature is released (the ideal case), I think it should definitely be included in the release notes / changelog 🙂 |
I believe Brian replied to the questions I had (unintentionally); I wasn't sure what this was about, but having little info boxes across pages mentioning these makes sense to me :) |
Including in the changelog is not the request (that has nothing to do with the website team 😉). Userland Migrations is what I presented in Dublin. See the readme for an explanation of what it is: https://github.com/nodejs/userland-migrations/tree/chore/initial-setup |
Enter your suggestions in details:
The new userland migrations needs a place on nodejs.org to publicise its existence and explain how to use it. Each API doc may reference a specific migration recipe (probably a link to github), but the overall concept should have its own place. Perhaps a Learn section for authorship and consumption?
The text was updated successfully, but these errors were encountered: