docs: add AEO cross-links for agents and orchestration - #453
Conversation
Link high-traffic agent docs to multi-agent orchestration pages so readers can continue from FAQs, slash commands, software factory, agents, and the cloud agents quickstart into parent/child orchestration workflows. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can follow along in the session on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds targeted internal links from cloud-agent, slash-command, FAQ, quickstart, and software-factory docs into the existing multi-agent orchestration pages. The added routes point to existing docs pages and the changes stay within the stated AEO/internal-linking scope.
Concerns
- No blocking concerns found.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
…08-03 Resolves conflicts from the agent-platform -> agents docs restructure: - Re-apply /orchestrate cross-link to relocated src/content/docs/agents/capabilities/slash-commands.mdx - Keep new Multi-agent orchestration bullet in software-factory.mdx with main's updated /agents/capabilities/skills path Co-Authored-By: Oz <oz-agent@warp.dev>
2 participants
Summary
Adds small, high-confidence internal cross-links so readers on agents/cloud-agent docs can continue into multi-agent orchestration docs.
AEO brief
Goal: Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs.
Recommendation: Update existing pages with natural cross-links (no new pages).
Source signals:
warp agent,oz agent, and related multi-agent/cloud-agent intent landing on Warp marketing and docs surfaces./orchestrate, parallel cloud agents, or software-factory role fan-out without linking to/platform/orchestration/or/platform/orchestration/multi-agent-runs/.Vocabulary map:
Pages touched:
src/content/docs/platform/faqs.mdx— multi-agent coordination FAQ already describes concurrent agents; link to orchestration model.src/content/docs/agent-platform/capabilities/slash-commands.mdx—/orchestraterow had no destination page; link to Multi-agent orchestration.src/content/docs/platform/software-factory.mdx— body already says Oz orchestrates specialized roles; add inline + Related pages link.src/content/docs/platform/agents.mdx— Related pages covered triggers/environments but not orchestration.src/content/docs/platform/quickstart.mdx— common use case mentions parallel cloud agents; next steps lacked orchestration path.Links added:
/platform/orchestration/— reader asking how concurrent agents coordinate needs the parent/child model./orchestrate→/platform/orchestration/— reader invoking the command needs the feature page./platform/orchestration/— reader learning role-based factory flow next needs fan-out/review swarm patterns./platform/orchestration/— next-step list for factory builders./platform/orchestration/— cloud-agent identity page readers often continue into multi-run coordination./platform/orchestration/— first-run readers who came for parallel agents get the concept page./platform/orchestration/multi-agent-runs/— after first cloud agent, next workflow is starting an orchestrated run.Reader next step:
Open questions for human review:
Test plan
python3 .agents/skills/style_lint/style_lint.py --changedpython3 .agents/skills/check_for_broken_links/check_links.py --internal-onlygit diff --checkorigin/mainReviewers
Please loop in docs/growth-docs reviewers (Rachael, Petra, Hong Yi, Danny, and other active
#growth-docsreviewers).Conversation: https://app.warp.dev/conversation/d2c46db4-7f2e-47e2-bf71-033492641180
Run: https://oz.warp.dev/runs/019fc823-8da1-7c1f-8fea-5be83c7ea3d5
This PR was generated with Oz.