Skip to content

Docs: Reorganize and move GMA to own page

Cynthia "Arty" Ng requested to merge docs-spt-2305 into master

What does this MR do?

Review of page as per OKR.

Changes include:

  • some minor edits
  • removing some repetitive language
  • fix technical errors
  • reorganizing sections to group like sections and move up some pertinent sections higher
  • moving GMA to its own page
  • updated tier badges

I know we weren't really supposed to be creating new pages, but GMA may be separate from SAML in the future and it was making the page really long without adding anything to it.

The main addition to the GMA page is a link to the issue where we're tracking enabling the feature. Because it says it was introduced in 12.1, people constantly ask why they don't see the option, and it's been delayed to an undetermined future milestone.

Related issues

Closes gitlab-com/support/support-team-meta#2305 (closed)

Author's checklist (required)

When applicable:

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

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Cynthia "Arty" Ng

Merge request reports