Create a information architecture for all docs needed

[lindydonna]

Create a tree of documentation titles and which section they should go into. This will then turn into individual issues that everyone can contribute to.

Example from Joe: how config precedence works.

[lindydonna]

Discussion about how to best structure the docs are in the #docs channel on Slack.

[ericrudder]

Setting to M11 to see M10 shutdown more clearly; fine to finish "early."

[lukehoban]

Let's find a way to "finish" this in M10 and open new issues on whatever concrete next steps we need to take. I believe we could call this done now - but I'll let @lindydonna make that call and decide what (if any) new items to open to track next steps.

[joeduffy]

I agree. Finishing this in M10 is essential to getting our velocity on docs to a good place in M11.

[lindydonna]

Let's keep this open until I've created all the new work items. I'll call this specific work item "done" when I have the skeleton in markdown rather than a doc. Should have this ready by EOD.

[lindydonna]

Initial work for doc structure is done in pr #70 . I'm creating new work items to track specific docs to be written.