Refactor and restructure environments page
What does this MR do?
This MR:
- Splits the content into configuration-related and operations-related sections
- Edits the whole document for clarity.
- Adds EE-only content to CE version, to narrow gap between the two.
See:
- Before: https://docs.gitlab.com/ce/ci/environments.html
- After: http://review-docs-docs-ayv5ea.178.62.207.141.xip.io/ce/ci/environments.html
Also Protected Environments (new to CE repo):
- Before (EE): https://docs.gitlab.com/ee/ci/environments/protected_environments.html
- After: http://review-docs-docs-ayv5ea.178.62.207.141.xip.io/ce/ci/environments/protected_environments.html
Ported to EE in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10335.
Related issues
Relates to the work in: https://gitlab.com/gitlab-org/gitlab-ce/issues/58451.
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the ~Documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Evan Read