doc: move topics/guides to website

[evanlucas]

This commit removes the topics and guides that the documentation
working group has proposed added to the website. We want them to have
more visibility and believe that moving them to the website does that.

This depends on nodejs/nodejs.org#1105 landing.

/cc @nodejs/documentation

Checklist

• commit message follows commit guidelines

Affected core subsystem(s)

doc

[gibfahn]

Maybe Fixes: https://github.com/nodejs/node/issues/10792 in the commit message?

[evanlucas]

@gibfahn good call. Thanks!

[gibfahn]

So looking at the line counts between this and nodejs/nodejs.org#1105, it looks like:

File	Move	Old line count	New line count
timers-in-node.md	straight move	-192	+192
blocking-vs-non-blocking.md	extra lines	-143	+148
domain-postmortem.md	extra lines	-301	+444
event-loop-timers-and-nexttick.md	extra lines	-486	+492
domain-resource-cleanup-example.js	gone	-136

Did domain-resource-cleanup-example.js get merged into something else?

[evanlucas]

Yes, I had to inline the js file.

[gibfahn]

LGTM, the diffs match up

[lpinca]

Rubber-stamp LGMT

[sam-github]

Thanks, Evan.

[evanlucas]

Landed in 7eef09d. Thanks!

[MylesBorins]

So I'm not sure what we want to do about this for LTS... It just dawned on me that in the past our guides were versioned... so the proper guide was with LTS.

Now we may have the wrong guides...

/cc @nodejs/lts

[MylesBorins]

ping @nodejs/lts again

[sam-github]

Only the API docs from LTS branches shows up on the website, so there isn't much reason to backport this, is there? Since we won't be cherry picking anything back that touches the guides, since they don't exist on the master, it won't even help avoid future conflicts.

[gibfahn]

So I'm not sure what we want to do about this for LTS... It just dawned on me that in the past our guides were versioned... so the proper guide was with LTS.

Now we may have the wrong guides...

When this was previously discussed in the docs WG, the general feeling was that we should do this first to get the guides more visible, and worry about things like multiple versions later. The alternative to this would be to do what we do with the api docs, but that's a lot more involved. Previously, no-one really knew that the user guides existed, so this is at least a step in the right direction.

[MylesBorins]

@gibfahn based on that, should we backport the removal?

[sam-github]

@MylesBorins I can't find any signs that the guides even show up on the website for older releases, am I missing it?

Given that, back-port or not is just a matter of what makes maintaing LTS easier. Since its just removing files, I don't think we need this, there won't be conflicts.

[gibfahn]

I can't find any signs that the guides even show up on the website for older releases, am I missing it?

@sam-github The new location is directly at https://nodejs.org/en/docs/guides/, so they're not tied to a release. The old guides weren't on the website at all, they just sat in the source tree.

based on that, should we backport the removal?

Either way is fine. Shouldn't be any problem to backport, but it shouldn't cause any problems if we don't. So let's say no.