| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -31,6 +31,7 @@ back in to the TSC. | |||
| 31 | 31 | * [Post-mortem](#post-mortem) | |
| 32 | 32 | * [Intl](#intl) | |
| 33 | 33 | * [HTTP](#http) | |
| 34 | + * [Documentation](#documentation) | ||
| 34 | 35 | ||
| 35 | 36 | #### Process: | |
| 36 | 37 | ||
@@ -270,6 +271,22 @@ Its responsibilities are: | |||
| 270 | 271 | + Defining and adding common structures to the dumps generated | |
| 271 | 272 | in order to support tools that want to introspect those dumps | |
| 272 | 273 | ||
| 274 | + ### [Documentation](https://github.com/nodejs/docs) | ||
| 275 | + | ||
| 276 | + The Documentation working group exists to support the improvement of Node.js | ||
| 277 | + documentation, both in the core API documentation, and elsewhere, such as the | ||
| 278 | + Node.js website. Its intent is to work closely with Evangelism, Website, and | ||
| 279 | + Intl working groups to make excellent documentation available and accessible | ||
| 280 | + to all. | ||
| 281 | + | ||
| 282 | + Its responsibilities are: | ||
| 283 | + | ||
| 284 | + * Defining and maintaining documentation style and content standards. | ||
| 285 | + * Producing documentation in a format acceptable for the Website WG to consume. | ||
| 286 | + * Ensuring that Node's documentation addresses a wide variety of audiences. | ||
| 287 | + * Creating and operating a process for documentation review that produces | ||
| 288 | + quality documentation and avoids impeding the progress of Core work. | ||
| 289 | + | ||
| 273 | 290 | ## Starting a WG | |
| 274 | 291 | ||
| 275 | 292 | A Working Group is established by first defining a charter that can be | |
| Back | FazBrowse Home | New Git URL |
0 commit comments