Goal
Make the "Beta" docs the main docs. Deprecate the legacy GitBook docs.
Proposed Solution
Approach (per Feb 6 Tech Daily): Do a straight migration, not a migration + upgrade.
- Copy-paste all remaining content from GitBook into Mintlify as-is ("Frankenstein patchwork")
- Move aggressively — don't try to polish or redesign content during migration
- Once everything is in Mintlify, deprecate GitBook entirely so no one touches it
- Fix issues iteratively as people find them post-migration
- Going forward, each team member owns the documentation for what they build — docs are no longer a single person's responsibility
Considerations
- The previous approach was waterfall-style (get Mintlify perfect, then switch). This led to a backlog that was hard to prioritize alongside other work.
- Every new feature currently adds content to legacy GitBook that will eventually need migration. Migrating now means new content goes directly to Mintlify, avoiding double-maintenance.
- Quality will be rough initially, but the team will improve it collaboratively over time.
Goal
Make the "Beta" docs the main docs. Deprecate the legacy GitBook docs.
Proposed Solution
Approach (per Feb 6 Tech Daily): Do a straight migration, not a migration + upgrade.
Considerations