Github is nice, but it does not allow the clarity of consumption enabled by readthedocs for documentation efforts. We would like to utilize readthedocs to generate a more approachable set of documentation around how we work and who we are.
User stories:
[x] As an documentation contributor I can evaluate my work on readthedocs
[x] As a documentation consumer I can find relevant information on readthedocs
Acceptance criteria:
[x] Readthedocs is integrated with this repository
[x] Readthedocs is properly displaying tagged version of master as stable that is publically available
[x] A dev environment exists tracking the dev branch of this repository that is not publically available
[x] A qa environment exists tracking the qa branch of this repository that is not publically available
Related links or issues:
29
Definition of Ready Checklist:
[ ] User-facing feature: provides story or A/C in Gherkin format, or
[ ] Architectural feature: provides technical A/C
[ ] Dependencies identified
[ ] Sized by team
RProduct Owner AScrum Master CEng. Lead ITeam
Definition of Done Checklist:
[ ] Acceptance Criteria tested and passing
[ ] Deployed on test environment
[ ] QA performed & issues resolved
[ ] Unit test and E2E coverage updated (if applicable)
Feature Description:
Github is nice, but it does not allow the clarity of consumption enabled by readthedocs for documentation efforts. We would like to utilize readthedocs to generate a more approachable set of documentation around how we work and who we are.
User stories:
Acceptance criteria:
Related links or issues:
29
Definition of Ready Checklist:
RProduct Owner AScrum Master CEng. Lead ITeam
Definition of Done Checklist:
REng. Lead, Team AScrum Master CIProduct Owner