**Current Situation:**
- The Deploy product lives in our repo in a sub folder
- The current documentation instructs the user to `git checkout` the release pipeline, switch to the `deploy-3` branch and `cd deploy`
- Users arriving at the repo on Github are presented with the //unstable// `main` branch
**Goal:**
- As discussed on the retreat end of October, we aim for
- Make the `main` branch explicitly //unstable// so that we can keep a simple developer workflow
- Provide places for users to go to that are not our release pipeline development repo, to we can offer a simple user workflow. This means:
- Rendering / generating documentation for all products and versions for users to access on a permanent URL
- Provide a place to access only Deploy, probably another Github repo, where:
- Users can `git pull` to follow our changes
- Users can download github provided zip files for different refs
**Acceptance Criteria:**
[] Users can get Deploy releases from a place outside our repo
[] Population of that place is automated
[] Documentation is updated accordingly
[optional] **Notes:**
- This goes hand in hand with setting up a place for documentation browsing
[optional] **Open Questions:**
-