Skip to main content

​
Mintlify Purge — Business Learnings

​
Context

Migrated from Mintlify branding to Choco branding across the entire SO1 platform documentation stack. This was a vendor-abstraction exercise — decoupling the documentation system identity from a specific vendor name.

​
Impact

  • 63 files modified across 16 git repositories within the so1-console monorepo
  • 9 documentation fragment directories renamed from docs/mint/ to docs/choco/
  • 1 GitHub Actions workflow retargeted from Dev4rno/mintlify-docs to choco-hq/choco-forge
  • Zero downtime — all changes are content/config level, no runtime impact

​
Operational Takeaways

  1. Vendor coupling runs deep: A single documentation platform name propagated into 63 files across agent specs, runbooks, API references, prompt templates, CI workflows, and methodology docs. Future vendor integrations should use abstracted names from day one.
  2. Monorepo submodule complexity: With 30+ nested git repos, a “simple” find-and-replace becomes 16 separate commits plus a parent commit. Tooling that understands submodule boundaries is essential.
  3. Fragment manifests as coupling points: The devarno.fragment.json pattern creates a tight coupling between each subproject and the documentation platform’s schema URL. Consider a local schema reference instead.
  4. Prompt templates carry vendor names: Role prompts (mintlify-master) and pipeline prompts reference vendor names in both content and directory paths. Prompt registries (index.json) need updating when names change.

​
Action Items

  • Update GitHub Secrets: rename MINTLIFY_SYNC_TOKEN → CHOCO_SYNC_TOKEN in the life-hacks repo
  • Verify choco-hq/choco-forge repository exists and accepts dispatch events
  • Update any external CI/CD references to old workflow filename (sync-to-mintlify.yml)
  • Audit remaining vendor-specific naming in other repositories outside this monorepo