Writers' guide to stumptown

[wbamberg]

We should have a document describing what stumptown-content looks like from the point of view of a technical writer. This should explain:

• at a high level, what stumptown-content and stumptown-renderer are, and how they relate
• at a high level, which bits of the stumptown-content repo are of interest to writers
• what kind of files these bits contain
• what recipes are for
• how reference pages are written
• how guide pages are written
• how landing pages are written
• how sidebars are specified
• what all the currently designed ingredients are, and how they are to be written (e.g. browser_compatibility, examples, etc etc)
• how to run stumptown-renderer to see the rendered version of the documentation pages

It does not need to go into the details of build-json or what the JSON interface looks like.

---

Acceptance criteria:

• doc is written and reviewed by stumptown-content team

[jmswisher]

Parking until strategy is clearer.

[wbamberg]

FWIW this is done: mdn/stumptown-content#197.