-
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
Add contribute link to navbar #7274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (2)
- apps/site/navigation.json: Language not supported
- packages/i18n/locales/en.json: Language not supported
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I think this is a good approach given the issues discussed
todo: we also need a redirect |
@joyeecheung this was your original idea. we now have:
can you think of anything else? |
Thanks for opening the PR! Looks good as far as I can tell, but I do wonder if we should keep the original contribute page and just leave a link in there to CONTRIBUTING.md, in case there are any external websites already linking to the removed page and the URL would be broken (if we think nobody is linking to it then it's fine to just remove, though it seems plausible to me). |
That's a good point although I think this redirect should help avoid breaking things: https://github.com/nodejs/nodejs.org/pull/7274/files#diff-5ca5a80a6f81808f1779e8216ad41ca807d50397070d24bc8b4cc72653c84f0bR268-R269 |
Oh right I didn't understand what it was doing at first. In that case LGTM, thanks! |
Description
Does the simplest thing we can to improve visibility of contribution, while avoiding some of the problems we encountered with the version support docs.
As @joyeecheung accurately points out, directly linking to this content is the best way to keep it up to date.
Open to iteration, but I wanted to advance the conversation with a concrete implementation.
Validation
See the preview build
Related Issues
closes #7237
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.