Open danielhonker opened 11 months ago
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.
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."
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.
[ ] Add verbiage to About this Handbook and Contributions to describe the scope
Stories