Pre-seed new content for the shared Crew/Ops Knowledgebase

We need to figure out what content Crew Ops and crews themselves will need to have at the ready and build a basic library to bootstrap the knowledge base. This is in addition to any documentation we convert over from the project google drive. Crew Ops will use it for help-desk-like support and troubleshooting articles. Crews themselves will be able to use the same content self-service, Also Crews can create their own content. Content will span multiple crews over all time. Each crew and user should be uniquely identified.

Identify content needed
Assign to project members best suited for each
add to shared Crew/Ops Knowledgebase, following consistent structure/formatting/templates
add appropriate KB tags

No files, tests, or entry points are named. Start by clarifying where the shared Crew/Ops Knowledgebase lives, which content is needed, and who will assign it; done means a consistently structured, tagged starter library with unique crew and user identification.

Written by the indexing model from the issue text.