Backfill blog links (Apr 10–16) - #38505
Open
jeff-morgan-dd wants to merge 2 commits into
Open
Conversation
…archy Part 2 of 4: Datadog blog posts published in Apr 10–16, 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>
Contributor
Contributor
|
jeff-morgan-dd
marked this pull request as ready for review
July 28, 2026 14:26
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
1 participant
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?
Backfills blog links to docs pages (posts published Apr 10–16, 2026). Second 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.