Workload Protection: Rename getting_started to setup, fix duplicate nav entries - #38528
Draft
drichards-87 wants to merge 4 commits into
Draft
Workload Protection: Rename getting_started to setup, fix duplicate nav entries#38528drichards-87 wants to merge 4 commits into
drichards-87 wants to merge 4 commits into
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Follow-up to #38502, targeting the Workload Protection revamp branch. Two changes:
1. Renames the
getting_startedsection back tosetup.Every other Datadog security product names this section "Setup" (Code Security, Cloud
Security Management, Application Security, Sensitive Data Scanner), and Workload
Protection used "Setup" before the revamp. "Getting started" is also the name of a
separate site-level section at
/getting_started/security/, so reusing it inside aproduct is ambiguous.
git mv(history preserved) and updates the nav label,identifiers, 8 nav URLs, 26 inbound links, and 3 tile partials.
eBPF, Windows). Their
setup/agent/*URLs are live onmaster, and the move togetting_startedhad left them without aliases. No aliases are added for thegetting_startedURLs themselves, since that path only ever existed on this branch.setup/_index.md. It was superseded by the moved index and its linkspointed at
setup/agent/*pages that no longer exist.2. Removes a duplicate Workload Protection nav block.
The revamp added a new nav block but left the tail of the old one in place, producing a
second "Workload Protection" top-level item and 4 duplicate menu identifiers
(
workload_protection,workload_protection_inventory,workload_protection_guides,workload_protection_troubleshooting). The removed entries were byte-identical to onesalready present in the new block, so nothing is lost.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes