Docs: ID highest-priority cleanups

Problem to solve

As part of onboarding into devopscreate, which is a large docset, I need to identify the highest-value pages to clean up first, as I don't have infinite hands.

Further details

The google doc with the master list of pages and their associated data.

• Column I: stage
• Column J: group
• Column L: word count for page (can be skewed by code examples, so make allowances)
• Columns O-AA: pageviews by month

Proposal

Identify the pages I should revise and clean up first. Take multiple factors into consideration, including:

• Pages with large numbers of visits
• Pages identified by PMs / EMs / UX as unusually important (for whatever reason). Ask the PMs which pages matter to them.
• Ensuring that each team (groupcode review, groupsource code, ~"group::editor", ~"group::ecosystem") benefits early on. While this will be an ongoing process, demonstrating commitment to all four groups matters here
• Pages identified by TW leadership in &4681
  • Source Code: https://docs.gitlab.com/ee/gitlab-basics/start-using-git.html (&3080) doc/gitlab-basics/start-using-git.md
  • Source Code: https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html
  • Source Code: https://docs.gitlab.com/ee/user/project/code_owners.html
  • Code review: https://docs.gitlab.com/ee/user/project/merge_requests/
  • Code review: https://docs.gitlab.com/ee/user/discussions/
  • Code review: https://docs.gitlab.com/ee/user/project/merge_requests/getting_started.html#reviewer - #273761 (closed) exists
  • Editor: https://docs.gitlab.com/ee/user/project/wiki/
  • Editor: https://docs.gitlab.com/ee/user/project/repository/web_editor.html
• Other factors that I will remember as soon as I hit Save.

The deliverables from this issue will be:

1. A set of pages identified for cleanup in %13.10. (Will be small, as we're already in this milestone.) Create issues for these pages, assign to Amy, add to current milestone.
2. A larger set of pages identified for cleanup in %13.11. Larger set, as I'll have the full milestone to work.
3. A duplicate of this issue (%13.11, assigned to Amy) to continue setting priorities for future milestones.

Who can address the issue

@aqualls

Other links/references