Add and restructure external resources and examples
What does this MR do?
Adds newer external resources to the CI section of the docs, and treats them more as examples.
Also clearly delineate between content that is in the doc suite and that outside the doc suite.
Ported in: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9737
Before:
- CI landing page: https://docs.gitlab.com/ce/ci/README.html
- CI examples page: https://docs.gitlab.com/ce/ci/examples/README.html
After:
- CI landing page: http://review-docs-docs-6ctf7r.178.62.207.141.xip.io/ce/ci/
- CI examples page: http://review-docs-docs-6ctf7r.178.62.207.141.xip.io/ce/ci/examples/README.html
Related issues
Closes: https://gitlab.com/gitlab-org/gitlab-ce/issues/58041
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
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