docs(ide-plugins/vscode): reorganize VS Code extension docs to lead with Code Security#37166
Conversation
…ith Code Security - Moved Code Security to the top of the feature list and Core features section in `_index.md` - Restructured page into Core features (Code Security, Code Insights, View in IDE, Fix in Chat) and Other features (Logs, Exception Replay, Live Debugger) - Added "in limited support" alerts to Logs, Exception Replay, and Live Debugger in `_index.md` and their respective subpages - Updated Code Insights description to focus on code and library vulnerabilities as the primary use case - Moved runtime errors and flaky tests to a new "Other insight types" subsection in `code_insights.md` with a limited support note - Reordered VS Code submenu in `main.en.yaml`: Code Security (101), Code Insights (102), Logs (103), Exception Replay (104), Live Debugger (105) K9VULN-15558
There was a problem hiding this comment.
Pull request overview
Reorganizes the VS Code/Cursor extension documentation to lead with Code Security, restructures features into "Core" and "Other" sections, marks Logs/Exception Replay/Live Debugger as in limited support, narrows Code Insights to focus on vulnerabilities, and reorders the sidebar menu accordingly.
Changes:
- Reorders feature listings and sidebar menu to place Code Security first; introduces a Core/Other features split.
- Adds "in limited support" alerts to Logs, Exception Replay, Live Debugger, and the runtime errors / flaky tests insight types.
- Narrows Code Insights to code/library vulnerabilities and moves runtime errors and flaky tests into an "Other insight types" subsection.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| content/en/ide_plugins/vscode/_index.md | Reorganizes feature list and sections; promotes Code Security to top; adds limited-support alerts. |
| content/en/ide_plugins/vscode/code_insights.md | Reframes Code Insights around vulnerabilities; moves other insight types to a limited-support subsection; reorders further_reading. |
| content/en/ide_plugins/vscode/logs.md | Adds limited-support alert. |
| content/en/ide_plugins/vscode/exception_replay.md | Adds limited-support alert. |
| content/en/ide_plugins/vscode/live_debugger.md | Adds limited-support alert. |
| config/_default/menus/main.en.yaml | Reorders VS Code submenu: Code Security (101), Code Insights (102), Logs (103). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
Opened DOCS-14603 to follow up with editorial review. |
…ith Code Security (#37166) - Moved Code Security to the top of the feature list and Core features section in `_index.md` - Restructured page into Core features (Code Security, Code Insights, View in IDE, Fix in Chat) and Other features (Logs, Exception Replay, Live Debugger) - Added "in limited support" alerts to Logs, Exception Replay, and Live Debugger in `_index.md` and their respective subpages - Updated Code Insights description to focus on code and library vulnerabilities as the primary use case - Moved runtime errors and flaky tests to a new "Other insight types" subsection in `code_insights.md` with a limited support note - Reordered VS Code submenu in `main.en.yaml`: Code Security (101), Code Insights (102), Logs (103), Exception Replay (104), Live Debugger (105) K9VULN-15558
What does this PR do? What is the motivation?
_index.md_index.mdand their respective subpagescode_insights.mdwith a limited support notemain.en.yaml: Code Security (101), Code Insights (102), Logs (103), Exception Replay (104), Live Debugger (105)Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
AI assistance
Additional notes
K9VULN-15558