Learning Path for Node.js

[mcollina]

I think we should examine the Learn section of our website and identify missing areas.

[AugustinMauroy]

as said I'm -1 to have a learning path in terms of "do that" -> that -> that.
May be "introduction to node" should be a basic of js with node.
And after subsection should be for area/module of node like Test-runner and typescript

[AugustinMauroy]

BTW: i had found this piece of doc. But very old it's from first part of nodejs.dev
https://github.com/nodejs/nodejs.dev/tree/7d89c22668101d972bf463d713c09834e9586dc8/src/documentation

[bmuenzenmeyer]

other notes from collab summit:

• the learning path is more like a graph than a linear path
• can we point to courses or books or videos? pandoras box / conflict of interest - see #amb
  node.js ambassadors / dev rel content - see ambassador docs
• can we find technical writers to help
• we should explore paying for this via open collective

[bjohansebas]

Maybe consider adding resources for HTTP/2? There is only a mention of HTTP/1

[AugustinMauroy]

For me, the parts we should have (in terms of subsection and order doesn't matter yet):

• Introduction: setting up what node is, reminder of JS, link to download. The difference between environments.
• Networking client: a reminder of what a request is, how to use node, how to use fetch behind a proxy.
• Networking server: Create a server with the HTTP module. Differences between HTTP1, HTTP2, HTTPS
• CLI: input, output, color, env, readline. REF #
• file system: different file system, read/write file, difference between node:fs and node:fs/promise.
• Test-runner: already correct maybe add real example
• typescript: already clean
• asynchronous flow: not expert so idk what we should put there
• Diagnostics: add links between existing resources and a bit of context