docs: add AEO cross-links for agents and orchestration#175
Draft
rachaelrenk wants to merge 1 commit into
Draft
Conversation
Add internal cross-links between agent/orchestration docs pages where orchestration concepts are discussed but not linked to the orchestration documentation. Pages touched: - planning.mdx: add orchestration link in Next Steps - harnesses/warp-agent.mdx: fix subagents link target, add orchestration cross-links in Cross-harness orchestration section - quickstart.mdx: add orchestration to What to explore next - platform.mdx: add orchestration docs link in Warp Orchestrator section - skills-as-agents.mdx: add orchestration to Related resources Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
This is a test run |
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.
Summary
Add internal cross-links between agent, cloud agent, and orchestration documentation pages where orchestration concepts are discussed or referenced but not linked to the actual orchestration docs.
Source signals
GSC_SERVICE_ACCOUNT_CREDENTIALS_JSONnot set)/planorchestration config, fan-out, parent/child model) without linking to the orchestration documentationPages touched (5 files, 7 links added)
agent-platform/capabilities/planning.mdx/planis a primary entry point for orchestration (the plan card surfaces an inline orchestration config). The orchestration docs (orchestration/index.mdx, multi-agent-runs.mdx) explicitly describe/planas an orchestration entry point, but planning.mdx didn't link back.agent-platform/cloud-agents/harnesses/warp-agent.mdx[subagents](/agent-platform/cloud-agents/overview/)→[subagents](/agent-platform/cloud-agents/orchestration/)— the link target was the generic overview page, but subagents are documented on the orchestration page.agent-platform/cloud-agents/quickstart.mdxagent-platform/cloud-agents/platform.mdxagent-platform/cloud-agents/skills-as-agents.mdxRejected candidates
agents.mdx: Focused on cloud agent identities/service accounts, not capabilities. Orchestration link would be tangential.handoff/index.mdx: Handoff and orchestration are distinct concepts. Handoff mentions "fan out variants" but in the context of local-to-cloud promotion, not multi-agent orchestration.scheduled-agents.mdx: Schedules and orchestration don't overlap directly.how-to-run-3-agents-in-parallel.mdx: Very short video-based guide with no Related/Next Steps section to extend.environments.mdx: Already links to relevant pages; orchestration isn't a natural cross-link from environment configuration.Validation
git diff --check— clean (no whitespace errors)npm run build— succeeds (336 pages, 0 errors)Open questions
how-to-run-3-agents-in-parallelguide could benefit from a Related Pages section linking to both orchestration and the comprehensive multi-agent guide, but adding a new section is a larger change than this PR's scope.Conversation: https://app.warp.dev/conversation/a76e6886-85d5-49c7-9cef-a497844260ea
Run: https://oz.warp.dev/runs/019e8eac-40e3-7d1a-b07c-69f5ab2426c2
This PR was generated with Oz.