Migrate cycle analytics topic to new section
What does this MR do?
Follows up from: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31460 and https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31572.
Created new index page for everything in the Analytics space. Migrates content for Project analytics into this new space.
Preview: http://review-docs-docs-pynh2j.178.62.207.141.xip.io/ce/user/analytics/index.html. Please click through the links to make sure it makes sense.
Just a simple redirect of Cycle Analytics content for now. I removed the image to save having to also migrate it, and fixed links as appropriate.
We could choose to split it if we want content just for a project's Project > Cycle Analytics separate to Analytics > Cycle Analytics.
WDYT @wortschi @valexieva @johnjeremiah
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.