Launch planning

Plan for going live.

Consider things like: a maintenance window, ensuring an available reviewer for bulk Docs content updates, ensuring infra support, a rollback plan, deploying pipeline changes to other projects. Document the timeline and steps to launch.

This work should include as close to a replica launch as possible (e.g, see what happens when we move a domain name from one Pages project to another).

Launch steps

Draft: https://gitlab.com/gitlab-org/technical-writing-group/gitlab-docs-hugo/-/merge_requests/284

Questions to answer

• What sort of training materials should we provide to TWs and contributors to help with the transition? (see gitlab-org/gitlab!178338 (merged))
• What do we need to do with links to docs from the UI? (see #43 (comment 2251442922))
• What markdownlint changes need to happen at launch time? (e.g, title handling) (see #178 (closed))
• What is the right order-of-operations for updating automated pages?
• How should we time manual updates (e.g, removing Kramdown syntax)?
• Does moving a domain from one Pages site to another require a DNS change?