JavaScript style guide for documentation PRs

@zachleat,

Can we drum up a quick style guide for vanilla JS code examples? I'm willing to forego my (otherwise highly opinionated) personal style for a standard.

I can mimic what's already there, but it'd be good to establish something formally—for consistency within the docs (if not also the codebase). Here are the major categories I'm thinking we could use some clear ground rules:

• Ternary operators v. conditional statements?
• Semicolon?
• Closures?
• Explicit return statements?
• var v. const and let?
• Arrow functions v. declarations v. expressions?
• When and when not to cache variables
• Classes v. exports.render
• Comments and/or JSDoc blocks?
• import v. require()
• this
• Others?

I'm convinced more folks would reach for the vanilla 🍦 if they had more examples in the docs—and I wanna help.

Start with the issue body and its 15-comment thread; no file or test is named. Determine whether the documentation PR style guide has a settled scope, then identify the documentation entry point and agree on the categories and examples that constitute completion.