Skip to content

Promote Advanced SAST to a direct child of SAST

Connor Gilbert requested to merge connorgilbert/promote-adv-sast-nav into main

What does this MR do and why?

What:

  • Move Advanced SAST out from under a sub-page.
    • Previous location:
      • Use GitLab
      • Secure your application
      • SAST
      • SAST analyzers
      • GitLab Advanced SAST
    • New location:
      • Use GitLab
      • Secure your application
      • SAST
      • GitLab Advanced SAST
  • Rename page to remove "analyzer".

Why:

  • I want to edit the Advanced SAST page to reflect the holistic workflow experience customers get when using it. This means concentrating less on its packaging as an analyzer, and more on Advanced SAST as a key capability and set of features (including the analyzer, but also UI features and more). These capabilities are part of the SAST category, not a subordinate topic to "SAST analyzers".
  • I'd like to improve discoverability of this page. Having it nested under "SAST analyzers" means that it isn't shown by default when a user is already reading SAST docs.
    • If they're already reading SAST docs, they're the exact folks we want to be sure know that Advanced SAST exists.

Screenshots, screen recordings, or links to review app

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Configure a local GitLab Docs environment: https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/setup.md.

Merge request acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports