-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Docs WG Call for Members #4573
Comments
✋ |
Hi @chrisdickinson, I'll be happy to help with what I can. I think, as @kosamari stated, some parts of the docs could really use improvements specially to abstract core concepts to a level that any user could understand, not only core contributors. |
As promised, I am now closing this issue — if you still want to help out with the Docs WG, fret not, you can sign up here. Thanks all! 👋 |
Hey all! 👋
As a heads up, there's talk going on in the node issue tracker about ratifying the Docs WG. As part of this, we've landed on a working proposal for where the docs will live. Per this proposal, the Docs WG will be working within the
nodejs/node
repo. This means that we can work to apply internationalization to the API docs as well. 🎉If you've been working on the docs and would like to become part of the Docs WG, please note your interest on this issue and we'll get you on board. There will be a meeting in late January to discuss the state of the proposal. You may want to take a gander at the contributing and getting-started docs, as well! They're not set in stone but they reflect the current ethos of the WG.
I'll close this issue in two weeks.
Thanks, all!
The text was updated successfully, but these errors were encountered: