Contribution guide consolidation

[kattni]

• Creates customisable versions of code and docs contribution guides
  • Requires changes to config.yml to use in a target repo.
• Adds a customisable feature request explanation guide
• Updates docs-tools testbed to include the guides.
• Cleans up code and docs guides.

Closes beeware/beeware#24

TODO:

• Check entire PR for TODO, and resolve.

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[kattni]

I'm not adding TODO to the spelling word list, so the builds will fail until you complete the TODOs in the feature request guide.

[freakboy3742]

I've just pushed updates from a review of the new content; this is looking really good.

For the benefit of other observers - Kattni and I have spoken in person about some next steps, including some additional re-organization of this content prior to integrating into Toga, Rubicon and Briefcase.

[kattni]

Round three ready:

• What: Implement a new feature - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/what/feature_implement_process/
• What: Translate content - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/what/translate_process/
• How: Work from a branch - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/git_feature_branch/
• How: Avoiding scope creep - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/scope_creep/
• How: Add a change note - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/pr_change_note/
• How: Submit a new issue - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/issue_submit/
• How: Translating content -https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/translate/
• Style: Documentation style guide - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/style/docs_style_guide/

[kattni]

Round four: final round! Ready:

• What: Fix an issue - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/what/issue_fix_process/
• What: Review a pull request - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/what/pr_review_process/
• What: Use the tools - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/what/tools_use_process/
• How: Submit a pull request - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/pr_submit/
• How: Pull request review - https://beeware-docs-tools--94.org.readthedocs.build/en/94/content_test_bed/how-to/contribute/how/pr_review_provide/

Additionally, the entire How do I contribute? section should have links to prerequisites and followup, where applicable.

Please check my commit for the rest of the changes.

[freakboy3742]

👍 Looks great - another mammoth effort!