docs(site): highlight augmenting existing ADO pipelines via stage generator#909
Merged
Merged
Conversation
Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com>
Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
jamesadevine
June 8, 2026 19:31
View session
jamesadevine
approved these changes
Jun 8, 2026
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
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.
Summary
Adds a mid-page section to the site landing page calling out that agents can augment existing Azure DevOps pipelines, positioned as a nice-to-have rather than a headline feature.
site/src/content/docs/index.mdx, placed between "Five security layers" and "Get started in minutes".target: stagegenerator: compile an agent into a reusable stage-level template that drops into an existing multi-stage pipeline, with a short YAML snippet and a link to the Target platforms reference.Test plan
Documentation-only
.mdxchange. Snippet andtarget: stagesemantics verified againstdocs/targets.md; internal link path matches existing/ado-aw/reference/targets/route.