[M] Let's figure out documentation!

[JLWade]

This ticket is track work around our team figuring out some new documentation strategies.

Acceptance Criteria:

• determine if draw.io (done - see below) , figma (figjam), and/or mural can hook into github for simplicity (eg. updating a diagram so that it automatically updates in github wiki or readme documentation)
• draw diagram to show process
• wiki page created to use by team (done) - https://github.com/bcgov/parks-data-register/wiki/API-Specification#searching-the-data-register
• Draw.io integration with Github (done) - request has been approved (https://github.com/BCDevOps/devops-requests/issues/1598) and tested (https://github.com/bcgov/parks-data-register/commit/a50afe17b9d2a232a6ff28f941786dab7e0af9ac)
• Team Documentation Guide (done) - created for team to capture what documentation lives where (document is a living work in progress, expectation is its updated as additional decisions are made by team)
• "Changes During Implementation Process" (done?) - async discussion started on Team Retro channel; further discussion/decisions to take place at Sprint 6 retro (Jan 24th).
• Other?

[ashley-dhillon]

Draw.io integration with Github request has approved by BCDevOps group (https://github.com/BCDevOps/devops-requests/issues/1598) . Daniel has confirmed that the Draw.io app is available to use on our DR repo - https://github.com/bcgov/parks-data-register/commit/a50afe17b9d2a232a6ff28f941786dab7e0af9ac