Backfill blog links (Apr 17–May 8) - #38506
Conversation
…ierarchy Part 3 of 4: Datadog blog posts published in Apr 17–May 8, 2026. Adds blog links to docs further_reading and reorders each touched list to the tag hierarchy (Documentation/Guide → Learning → Blog → Release Notes → External). Irrelevant blog↔doc pairings pruned. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
![datadog-datadog-prod-us1-2[bot]](https://avatars.githubusercontent.com/u/365230?s=60&v=4){kind=small}
There was a problem hiding this comment.
More details
The changed pages preserve valid Hugo front matter and further-reading behavior, including the intentional move of Data Observability documentation links into the page body and the new partials. Direct validation found no duplicate or malformed targets; the full Hugo build was blocked only by unavailable external dependency access in the sandbox.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 4802ff3 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
5 participants
What does this PR do? What is the motivation?
Backfills blog links to docs pages (posts published Apr 17–May 8, 2026). Third of a few PRs broken up for review manageability.
This PR also reorders the Further Reading links where relevant in touched files only, to be consistent with the agreed-upon FR link tiers/order documented in DOCS-13928.
Merge readiness
For Datadog employees:
⚠️ Your branch name MUST follow the / 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
Claude did a relevance pass on blog<>doc pairings, did the link reordering, and double-checked link validity.
Additional notes
Testing: Links were scraped via API and implicitly are all 2xx/working links. As mentioned above, i also had Claude explicitly check successful resolution for all included links. So a spot-check at most should be sufficient for testing the PR, links have been tested.