Skip to content

Workload Protection: Rename getting_started to setup, fix duplicate nav entries - #38528

Draft
drichards-87 wants to merge 4 commits into
theop-dd/workload-protection-doc-v2from
deforest/wp-tier1-correctness
Draft

Workload Protection: Rename getting_started to setup, fix duplicate nav entries#38528
drichards-87 wants to merge 4 commits into
theop-dd/workload-protection-doc-v2from
deforest/wp-tier1-correctness

Conversation

@drichards-87

@drichards-87 drichards-87 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

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_started section back to setup.

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 a
product is ambiguous.

  • Moves the 8 pages with git mv (history preserved) and updates the nav label,
    identifiers, 8 nav URLs, 26 inbound links, and 3 tile partials.
  • Restores redirects for the five platform pages (Docker, ECS/EC2, Kubernetes, Linux
    eBPF, Windows). Their setup/agent/* URLs are live on master, and the move to
    getting_started had left them without aliases. No aliases are added for the
    getting_started URLs themselves, since that path only ever existed on this branch.
  • Deletes the old setup/_index.md. It was superseded by the moved index and its links
    pointed 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 ones
already present in the new block, so nothing is lost.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <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.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

@drichards-87 drichards-87 added WORK IN PROGRESS No review needed, it's a wip ;) Do Not Merge Just do not merge this PR :) labels Jul 28, 2026
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Jul 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Removed or renamed files (these should redirect)

Renamed files

Modified Files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend Do Not Merge Just do not merge this PR :) WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant