cc @nodejs/documentation

Thanks for PR'ing this in! The Docs WG is going to discuss next steps on adding guides in tomorrows meeting at 10AM PST; we'll take action on the PR shortly after that.

Please word-wrap at 80 characters, as per https://github.com/nodejs/docs/blob/master/STYLE-GUIDE.md

@bengl 80 characters does not work for lists. The list will force a newline. :/

@Fishrock123 I don't think that's so — for example:

• Hello there.
  I am wrapped.
• I am wrapped too
  But it's okay.

Source:

* Hello there.
I am wrapped.
* I am wrapped too
But it's okay.

Edit, if that's too ugly:

• Hello there.
  I am wrapped.
• I am wrapped too
  But it's okay.

* Hello there.
  I am wrapped.
* I am wrapped too
  But it's okay.

Will work too!

@chrisdickinson I don't think this is necessarily consistent between parsers/renderers then:

(Atom's markdown preview)

@bengl I consolidated the instructions into one list. :)

@Fishrock123 you mention a few times how much faster it is -- out of curiosity, could you quantify it?

@jbergstroem you mean /usr/bin/time it or what it seems to be?

I'd say it's at least 40% faster

@Fishrock123 so ninja vs make -j${cores}? Didn't think it was that much faster. Wow.

@jbergstroem well, that's how much faster it feels so maybe it isn't idk.

Just tested it locally:

• time spent: ninja was 10% faster
• cpu time: 4% less spent

ping @bengl & @chrisdickinson

ok LGTM 👍

@bengl Updated a bit (I wasn't comfortable with some statements), PTAL.

@chrisdickinson I still haven't shortened the lines... do we need to take it back to the docs WG? My editor renderer does not render split lines very nicely.

I'm going to land this tomorrow (Tuesday) unless there is additional review. We can fix any problems with it after I guess.

Whoops, missed this. Yep, LGTM.

@chrisdickinson do doc wg members officially have sign-off rights for doc/? I forget..

LGTM too. 👍