docs(i18n): 补齐英文版 Task Orchestration 概念翻译 / Translate Task Orchestration to English#14
Merged
Merged
Conversation
The concept chapter 04-concepts/10-task-orchestration was missing from the English locale, causing broken cross-chapter links from user-guide pages that want to point to "Team mode vs swarm mode" discussion (e.g., the new Team Version Management chapter). Mirrors the existing zh-Hans source 1:1 with the same mentor-style, customer-facing voice used in the other 04-concepts/* English files. Build verified: pnpm build passes for both zh-Hans and en locales, no broken links.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Adds the missing English locale version of the “Task Orchestration” concept page so that cross-chapter links (especially from user-guide content) no longer break in the English build.
Changes:
- Add
04-concepts/10-task-orchestrationEnglish translation underi18n/en/...with structure aligned to the Chinese source. - Use established in-repo linking patterns (relative concept links like
./step-types, and cross-chapter markdown-path links to user-guide pages).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
yi-ge
added a commit
that referenced
this pull request
May 17, 2026
1. 09-team-version-management.md line 64: replace "as a release" wording with "as a commit" — the remote-config step records a snapshot, the actual release flow is documented separately later. 2. Glossary: change ASCII parentheses to full-width parentheses on the two new Team entries, matching the rest of the zh-Hans glossary format (Teach（教）, Tool（工具）...). 3. Glossary (zh + en): reorder the three new Team entries alphabetically — Team Member Lock → Team Release → Team Version Management — so the T section stays navigable. 4. English 09 Next Steps: re-add the link to Intelligent Task Orchestration now that PR #14 has merged the English translation of that concept page.
4 tasks
yi-ge
added a commit
that referenced
this pull request
May 17, 2026
* docs: add Team Version Management chapter (zh + en) New chapter explains how a whole team can be versioned, pushed to GitHub/Gitee, released to the community, and one-click installed from someone else's link — written in the same mentor-style, customer-facing voice as the existing single-Agent Version Control chapter. Changes: - New docs/02-user-guide/06-agents/09-team-version-management.md (zh-Hans, main source) - New i18n/en/.../09-team-version-management.md (English mirror) - 08-version-control.md "Next steps" links to the new chapter (zh + en) - Glossary adds 3 entries: Team Version Management / Team Member Lock / Team Release (zh + en) Covers, in plain-language customer voice: - Why a team needs versioning - Two-layer model (team-level vs member-level) - 4 member sources (local / git / marketplace / built-in core) - Connecting a remote repo (GitHub/Gitee) - Viewing history, push/pull, upgrading members, releasing a new version - Installing from someone's link (forking) - Disband-as-archive (recoverable) - 5 common scenarios Build verified: pnpm build passes for both zh-Hans and en locales, no broken links. Related to desirecore PR #656. * docs: address Copilot review on PR #12 1. 09-team-version-management.md line 64: replace "as a release" wording with "as a commit" — the remote-config step records a snapshot, the actual release flow is documented separately later. 2. Glossary: change ASCII parentheses to full-width parentheses on the two new Team entries, matching the rest of the zh-Hans glossary format (Teach（教）, Tool（工具）...). 3. Glossary (zh + en): reorder the three new Team entries alphabetically — Team Member Lock → Team Release → Team Version Management — so the T section stays navigable. 4. English 09 Next Steps: re-add the link to Intelligent Task Orchestration now that PR #14 has merged the English translation of that concept page.
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
04-concepts/10-task-orchestration.md此前只有中文版,英文 locale 缺失,导致从 user-guide 章节(如"团队版本管理"等)指向"团队模式 vs 蜂群模式"概念解析的跨章节链接在英文版会 broken。本 PR 补齐英文翻译。04-concepts/10-task-orchestration.mdpreviously had only a Chinese version, while the English locale was missing. This caused broken cross-chapter links from user-guide pages (e.g., the upcoming Team Version Management chapter) that point to the "Team mode vs swarm mode" concept article. This PR adds the English translation.改动 / Changes
i18n/en/docusaurus-plugin-content-docs/current/04-concepts/10-task-orchestration.md翻译策略
04-concepts/*英文文件一致的导师式、客户向语气./step-types/./receipt-system(与现有英文 04-concepts 文件一致)../02-user-guide/04-delegation/06-cross-agent.md(避免英文版未译概念引发 broken link)验证 / Verification
pnpm build通过(zh-Hans + en 两个 locale)onBrokenLinks: 'throw'模式下无失效链接关联 / Related
发现于 PR #12 ("团队版本管理章节") 的 build 过程中。该 PR 当时为绕开 broken link 在英文 Next Steps 删除了一条到本文件的链接;本翻译合入后可在那个 PR 上追加补回。