Proposal to move guides to nodejs/nodejs.org

[evanlucas]

@nodejs/documentation would like to move all of the guides that are not directly related to contributing to core out of this repo and into the nodejs/nodejs.org repo. This is a tracking issue so we can bring it up at the next ctc-meeting.

This has come about in response to the latest docs wg discussion at nodejs/docs#119.

We propose that the following guides be moved:

• https://github.com/nodejs/node/blob/master/doc/guides/timers-in-node.md
• https://github.com/nodejs/node/blob/master/doc/topics/blocking-vs-non-blocking.md
• https://github.com/nodejs/node/blob/master/doc/topics/event-loop-timers-and-nexttick.md
• https://github.com/nodejs/node/blob/master/doc/topics/domain-postmortem.md

[sam-github]

I also think https://github.com/nodejs/node/blob/master/doc/topics/domain-postmortem.md should be moved to a documentation/Website guide, it includes important information on the limitations of Domains, and gives context to their deprecation.

Thoughts?

cf. nodejs/docs#119 (comment)

[evanlucas]

Thanks @sam-github. I updated the OP.

[jasnell]

Definitely in favor of this. Moving the guides out ought to give them greater visibility. +1

[Trott]

+1 for sure

[targos]

+1

[rvagg]

Is the domains postmortem doc in a good enough format for publishing in the website? Its original intent was to simply record the collection of problems that we had with domains in a single place we could point to rather than trying to regurgitate it each time we were asked.
/cc @trevnorris

[sam-github]

That's exactly why its worth having on the website. I'm not about to claim an energetic editor couldn't improve it, but its perfectly readable, serves its purpose, and yet isn't in a place its easily discovered. We can wait until people post github issues, then close them and point into the nodejs/node doc/topics directory, but I suggest its better to just put it on the website and link to from the domains API page.

[Qard]

Indeed, I would say it could use some editing, but I wouldn't want that to block this request. We could move it with the other docs and edit it after the transition, or we could leave it here and rewrite it in the website repo. I'm good with either, but I feel like keeping it in one location is probably best.

[Trott]

Including the +1 votes from @evanlucas and @targos here with the 10 votes from the CTC meeting today, that's 12 CTC members in favor, which is a majority. Removing the ctc-agenda label. Please feel free to proceed. Thanks!