-
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
docs.new.nodejs.org #8
Comments
I just happened to take a look at the Website WG's repos, and I noticed doc-tool is in there. It needs to be discussed if that should still be maintained by the Website WG, or if that should be handed over to the Documentation WG. I think it would be ideal for the Website WG to maintain it, as the Documentation WG isn't really centered around the building of the docs website so much as it is the content of the docs website. |
Is doc-tool the old documentation builder or the new one? |
I have a self-assigned task for figuring out the doc tooling for the docs WG. |
Closing, this tool isn't finished and we're moving towards merging content directly into the website. |
We should probably take this opportunity in building this repo out to take a more active role in the docs maintenance, since no one WG has really laid claim over it yet. Unless @nodejs/build has? Or maybe we should make a @nodejs/docs WG?
The text was updated successfully, but these errors were encountered: