Outdated documentation removal

What does this MR do?

Removes outdated documentation

On April 18th - GitLab 16.11 gets released, so ideally we should merge this on April 19th so the content is live with version 17.0

Related issues

#443453 (closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product tier badge under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

changed milestone to %17.0

added docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @faleksic

added Support Team Contributions label

added analytics instrumentation analytics instrumentationreview pending development guidelines labels

	1 Warning
	61b3e806: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.

	2 Messages
	This MR contains docs in the /doc/development directory, but any Maintainer (other than the author) can merge. You do not need tech writer review.
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/administration/settings/usage_statistics.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Category	Reviewer	Maintainer
analytics instrumentation	@bastirehm (UTC+2)	Maintainer review is optional for analytics instrumentation

Please check reviewer's status!

• Reviewer is available!
• Reviewer is unavailable!

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

Hello @bastirehm would it be possible to review these changes? This MR is related to the changes outlined in gitlab-com/support/support-team-meta#5824 (closed)

added docs-only label

requested review from @bastirehm

added analytics instrumentationapproved label and removed analytics instrumentationreview pending label

added 1 commit

• 7ffd2fbf - Remove broken anchor

Compare with previous version

changed the description

removed review request for @bastirehm

requested review from @lciutacu

resolved all threads

approved this merge request

Hi @lciutacu ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. You're welcome to improve it.

added Technical Writing label

enabled an automatic merge when the pipeline for 225a373e succeeds

merged

mentioned in commit 9ce617d4

mentioned in incident gitlab-org/quality/engineering-productivity/review-apps-broken-incidents#1513 (closed)

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowproduction label and removed workflowcanary label

added workflowstaging label and removed workflowproduction label

added workflowpost-deploy-db-staging label and removed workflowstaging label

mentioned in issue gitlab-com/support/support-team-meta#5981 (closed)

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label