Developer Notes on Repo Layouts

[ryanmrichard]

PR Type

• [ ] Breaking change
• [x] Feature
• [ ] Patch

Brief Description

In preparing ParallelZone's developer documentation I had put some notes together explaining what the various directories and files were. I then realized that most of our repos are set up in the same way so it probably makes more sense for that documentation to live here.

Not In Scope

I didn't go into full details of how the include/, src/, and tests/ directories should be structured. If we want to hammer that out now we can, and I'll update the PR. Otherwise, we can tackle that at a later point in time.

PR Checklist

• [x] Documentation (comments, API, user, design, and developer as applicable)
  • API
  • User
  • Design
  • Developer
• [x] Testing (unit, integration, performance, as applicable)
  • Unit
  • Integration
  • Performance
• [x] Code adheres to organization standards
  • C++
  • Python
  • Doxygen Conventions
  • reST Conventions

[ryanmrichard]

This PR also shortens the link list in the PR templates and creates a new developer topic "conventions" (which also subsequently required some refactoring to bring all the conventions together).

[ryanmrichard]

🚀 [bumpr] Bumped! New version:v0.1.0 Changes:v0.0.10...v0.1.0