Set up mkdocs site in Engineering CoP

[fyliu]

Overview

We need the Engineering documentation to be using mkdocs so that we can easily copy sections from the website or our docs over to it when needed.

The idea is to move generally-useful engineering docs from the website docs or our docs over to engineering so that other teams can reference them as well.

Action Items

• [x] Propose to Engineering CoP that they start hosting documentation that's common to different hackforla teams
• [ ] Ask that they set up an mkdocs site for the documentation, because both PD and the website will be using it
• [ ] Check that they have a working mkdocs site
• [ ] check and release #164 from ice box

Resources

• website's how to resolve merge conflicts guide
• website's resources for setting up mkdocs
• PD's old sphinx doc site's page on git

[fyliu]

I'm having trouble coming up with most of the labels for this. Maybe this should exist in Engineering instead? This was from the discussion where any guides that has to do with generic tools like git should be moved to the Engineering docs. I thought that it would be easier if we set up an mkdocs instance there so we can just copy/paste the content, even if it has some mkdocs-specific markup.