Confirm scope of the handbook

[danielhonker]

Notes on this (will groom the issue)

• Define scope of what goes in the handbook. What is too specific to one practice area. Concerned about scope creep.

• Will have some practice-area content -- career growth, competencies -- will be available to everyone.

• Want to keep the handbook as broad and Bloom-wide as possible. Don't want to have to manage practice-area content.

• Could also encourage practice areas to have their own mini handbooks for their specific tools, challenges, etc. Publishing those guides will be helpful for teams, and for RFP response.

  • Current examples: PDM guide, Engineering at Bloom
  • Also want a Manager's Guide (but not there yet)

• Add verbiage to About this Handbook and Contributions to describe the scope

Stories

As a handbook contributor, I want to know what to include in the Handbook, so that I can confidently write and review Handbook content.

As a Bloomer, I want to know what I can expect to find in the Handbook, so that I can look in the right place for stuff.

[danielhonker]

There doesn't seem to have been any confusion about what content goes in the handbook vs other docs. As we generate more practice-area or topic-specific guides, more questions might arise. Let's do this sooner so that we head-off questions.
Perhaps we add some language to Contributing to help people understand what goes in the handbook vs other docs.

[coreycaitlin]

Todo: Add section to CONTRIBUTING.md called "what goes in the handbook?" to describe scope, which is "Bloom-wide policy and guidance that can be public."