Skip to content

docs(channel-deployment): rebrand COCO → OpenMax in EN & ZH guides#180

Merged
tyler-0xffff merged 1 commit into
openmaxai:mainfrom
Eriche985:rebrand/channel-deployment-openmax
Jul 20, 2026
Merged

docs(channel-deployment): rebrand COCO → OpenMax in EN & ZH guides#180
tyler-0xffff merged 1 commit into
openmaxai:mainfrom
Eriche985:rebrand/channel-deployment-openmax

Conversation

@Eriche985

Copy link
Copy Markdown
Contributor

Summary

Per the brand upgrade to OpenMax, replace all remaining COCO brand mentions in both language versions of the channel-deployment guide (docs/getting-started/channel-deployment.md + docs/zh/getting-started/channel-deployment.md).

Changed (brand copy only)

  • COCO DashboardOpenMax Dashboard (headings, steps, tables, image alt text) — matches the convention already used in the MS Teams section
  • COCO Account / COCO账号 → OpenMax Account / OpenMax账号
  • Example names: COCO AI Employee / COCO AI 员工 / My COCO AI / COCO AI → OpenMax equivalents; my_coco_ai_botmy_openmax_ai_bot; bot handle coco-ai-employeeopenmax-ai-employee; COCO Bot SecretOpenMax Bot Secret
  • MS Teams manifest sample (ZH): developer name COCOOpenMax, app name & description
  • Prose: "your COCO agent" → "your OpenMax agent", "COCO handles everything" / "由 COCO 代为处理" → OpenMax

Deliberately NOT changed

  • Live URLs/domains: icoco.ai/dashboard, docs.icoco.ai/*, <subdomain>.icoco.ai webhook examples (product URLs still live on these domains)
  • Image file paths (e.g. /coco-dashboard-*.png) — renaming images would re-trigger the CDN cache issue fixed in fix(channel-deployment): cache-bust MS Teams tutorial images (rename to -v2) #178; filenames are invisible to readers
  • GitHub release asset links (github.com/openmaxai/coco-materials/...)

Verification

  • grep -i coco residue check: zero brand-text matches left; remaining matches are only domains/file paths/repo URLs
  • vitepress build passes locally (EN + ZH render clean)

109 replacements per side, text-only, no structural/link/anchor changes.

🤖 Generated with Claude Code

Replace all COCO brand mentions (Dashboard name, account, example app/bot
names, manifest samples, agent references) with OpenMax in both language
versions of the channel-deployment guide.

Deliberately unchanged: live URLs/domains (icoco.ai, docs.icoco.ai,
webhook subdomains), image file paths, and GitHub release asset links.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@tyler-0xffff tyler-0xffff left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: PASS ✅

Verified against 3 checkpoints:

① Brand text only, no collateral damage

  • Image withBase(...) count identical to main: EN 85/85, ZH 67/67
  • HTTP link count identical to main: EN 30/30, ZH 27/27
  • All product URLs preserved (icoco.ai/dashboard, docs.icoco.ai/privacy-policy, docs.icoco.ai/user-agreement, webhook subdomains), image file paths untouched (correctly avoids re-triggering the #178 CDN-cache-404 issue), GitHub release asset links untouched.

② Full zh + en coverage, no brand-text residual

  • Residual grep on both files: no remaining brand-text COCO. All leftover "coco" strings are exclusively the intentionally-kept icoco.ai domain, coco-materials release assets, and /coco-dashboard-*.png image paths.
  • Consistent with existing MS-Teams section wording (COCO Dashboard → OpenMax Dashboard, example names, Teams manifest name/developer/description, Azure bot handle, secrets label).

③ Build

  • vitepress build docs → exit 0, pages rendered, sitemap generated. (Pre-existing cosmetic @import order warning in theme CSS, unrelated to this PR.)

Post-deploy I'll verify live on both docs.icoco.ai and docs.openmax.com.

@tyler-0xffff
tyler-0xffff merged commit 7369b4c into openmaxai:main Jul 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants