Launch planning
Plan for migrating the new build back into the gitlab-docs project and going live.
We'll probably need to account for a maintenance window, an available reviewer for bulk Docs content updates (e.g, bulk front matter changes), a rollback plan, and deploying build/linting images to other projects. Document the timeline and steps to launch.
Launch steps
Incomplete and in no particular order yet:
- Rename index files
- Run migrations against actual content
- Set the
HUGO_LAUNCH_VERSION
constant inthemes/gitlab-docs/src/helpers/constants.js
- Move code into the
gitlab-docs
project
Questions to answer
- How should we time manual updates (e.g, removing Kramdown syntax)?
- What pages will need redirects? (e.g, pages where we're dropping the
/ee/
prefix) - What all will need to happen to migrate back to the
gitlab-docs
namespace? (e.g, find/replace the project URL in project docs, change a project setting, etc)
Edited by Sarah German