[DOCS-14082] Restructure Agentic Onboarding setup page#36655
Draft
domalessi wants to merge 12 commits into
Draft
[DOCS-14082] Restructure Agentic Onboarding setup page#36655domalessi wants to merge 12 commits into
domalessi wants to merge 12 commits into
Conversation
Reorganize the page into three top-level paths (Setup CLI, MCP Server, Skills) and update content per Vidur's draft. Skills section is a placeholder pending the public Skills release. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Standardize "MCP Server" capitalization, restructure the Cursor install tab as two distinct methods, replace afterthought em dashes with periods or restructured clauses, and rephrase "and so on" trail-offs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Expand IaC on first mention, harmonize the Overview table cells as single sentences with a parallel "You..." opener, and replace generic MCP and Skills H3 headings with retrieval-friendly variants. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
domalessi
commented
May 13, 2026
Contributor
Author
domalessi
left a comment
domalessi
left a comment
There was a problem hiding this comment.
Three open questions flagged below for Vidur's pass — none blocking the structural rewrite, but worth deciding on before the Skills section lands.
| Agentic Onboarding lets LLM coding agents instrument your applications and infrastructure for [Error Tracking][1], [Real User Monitoring (RUM)][2], [Product Analytics][3], [Infrastructure Monitoring][4], and [Serverless Monitoring][5]. | ||
|
|
||
| Your coding assistant, such as [Cursor][1] or [Claude Code][2], detects your project's frameworks, adds configuration, and provisions required tokens and apps directly from your IDE. | ||
| There are three ways to get started. Pick the one that matches how you work: |
Contributor
Author
There was a problem hiding this comment.
Should this section call out prereqs for each path? For example: Node.js for the Setup CLI, an existing Datadog account + role permissions for the MCP Server, a Claude subscription (and which Claude surface) for Skills. Or fine to leave implicit / assume the audience will know what's required for each?
| | [Skills](#skills) | You're using Claude and want a focused skill for a single onboarding step (such as installing the Agent or enabling a cloud integration) rather than a full MCP toolset. | | ||
|
|
||
| ## Setup | ||
| The three paths are complementary and work against the same Datadog account. You can install the Datadog MCP Server in your IDE, run the CLI in a terminal, and invoke skills from Claude. |
Contributor
Author
There was a problem hiding this comment.
Each section below has a different internal structure: Setup CLI opens with a "what it can do" bullet list, MCP Server opens with a Supported frameworks table, Skills opens with an Available skills table. Probably intentional since the paths genuinely differ, but flagging in case we want to harmonize the openers.
| Skills work standalone, so you don't need the MCP Server installed to use them. After the skill completes, see [Next steps](#next-steps). | ||
|
|
||
| ### Deploy your app to production | ||
| ## Next steps |
Contributor
Author
There was a problem hiding this comment.
Your original draft had a placeholder for Troubleshooting in Next steps that I dropped. Can add back when we create a Troubleshooting page.
Items are verb-phrase fragments, so they take no end punctuation per the editorial standard. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Lead with the interactive no-flag command and present --product as a shortcut. This matches the progression in the Example flows section below (first-time user before existing-account) and lets readers run a command before learning the product identifiers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Both paths produce local file changes that must be committed and deployed, but the Skills path doesn't always. Move the commit + env var instructions out of Next steps and into each applicable section, leaving Next steps as a single universal verification step. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Each cell now carries a single decision-driving sentence; examples and mechanics live in the section the row links to. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fold the example-flows content into the Install and run section as
definition-style bullets. Each bullet leads with the user situation
("First-time user" / "Existing account") and shows the matching
command. Drops the separate Example flows H3.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the "matches your situation" framing, rephrase the two bullet labels for parallel state-plus-intent structure, and convert the post-bullet paragraphs into a three-step procedure. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fold the two command alternatives into step 1 as bold-prefixed continuation paragraphs. The whole Install and run section is now one four-step numbered procedure. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bring back the secret-manager propagation guidance from the original draft. It's a distinct concern from the per-section deploy step (which only covers commit + production env vars) and fills out the Next steps section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Lead with the recommended deeplink method and tuck the manual configuration into a collapse-content block. Matches the JetBrains tab pattern in bits_ai/mcp_server/setup.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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?
Fixes DOCS-14082
Restructures the Agentic Onboarding setup page into three top-level paths (Setup CLI, MCP Server, Skills) so the CLI surfaces as the primary entry point. Updates content per the draft reviewed with the product team:
error-tracking,rum,product-analytics,kubernetes,docker,serverless).agentic_onboarding: [gov,gov2]is already inconfig/_default/params.yaml)._index.mddescription updated to reflect the three-path structure.content/en/product_analytics/agentic_onboarding.mdandcontent/en/real_user_monitoring/application_monitoring/agentic_onboarding.mduseinclude-markdownand pick up the restructured content automatically.Open questions
gov, notgov2, which implied the CLI was usable on gov2. The new global site-support banner (agentic_onboarding: [gov,gov2]) blocks the entire page on both. Confirm with the product team whether the CLI actually supports gov2 before flipping to ready-for-merge — if it does, the global banner is over-blocking and we need a per-path approach.Merge instructions
Merge readiness:
Additional notes
Draft pending follow-up review with the product team to finalize the Skills section before flipping to ready-for-merge.