Audit
We inventory every page, mark the duplicates and the dead ends, and write a migration map that says what moves, what merges and what gets deleted.
Documentation migration studio
Documentation migration onto a stack you own
voix moves product documentation off locked proprietary platforms and onto an open-source stack your team owns. We audit what you have, restructure it, implement it in Docusaurus, train your writers and engineers, wire publishing into CI/CD, and hand over the repository. What you keep is Markdown in Git and a build you can run yourself.
docs/guides/authentication.md
@@ vendor export → docs/ in your repo @@
-<div class="wysiwyg" data-block-id="b71f0e2">
- <h2 style="font-size:18px;color:#333">Authentication</h2>
- <p><span style="font-family:Arial,sans-serif">Send your
- key in the </span><code style="background:#eee">
- Authorization</code><span> header.</span></p>
-</div>
+---
+title: Authentication
+description: Send your API key in the Authorization header.
+sidebar_position: 2
+---
+
+## Authentication
+
+Send your key in the `Authorization` header.
The problem
What platform lock-in actually costs a docs team#the-problem
Lock-in rarely arrives as a single invoice. It shows up as content you cannot open, contributors who are not allowed to contribute, and an export button that returns markup instead of documentation.
- The format
- Your pages live in a vendor database behind a WYSIWYG editor. The source of truth is an internal representation nobody outside the platform can open, diff, grep or script against.
- The seats
- Publishing is priced per seat, so the engineer who knows the answer is not the person allowed to write it down. Contribution gets rationed to whoever holds a licence.
- The search
- You get the search the vendor ships. You cannot tune the ranking, boost the pages support sends people to every day, or find out why the right page came fourth.
- The review gate
- There is no pull request, no second reader, no automated link check, and no way to ship a documentation change in the same review as the release it describes.
- The export
- The export button returns markup, not content: nested divs, inline styles and vendor data attributes. It technically leaves the platform. It does not arrive anywhere useful.
What we do
Four services, sequenced into one engagement#what-we-do
A migration usually needs all four, in this order: the structure first, then the platform, then the people who keep it current, then the pipeline that publishes it.
01
Consolidation and information architecture
We collect documentation and data scattered across wikis, tickets, slide decks and the old platform, then put it into one searchable, maintainable structure.
02Modern platform implementation
We implement a documentation platform your company owns, with reusable templates, navigation standards and a quality baseline the team can hold to.
03Employee onboarding and enablement
We train your people to author, review and publish, so the team ships documentation independently once the engagement ends.
04CI/CD documentation delivery
Updates are reviewed, tested and published consistently, which lowers release risk and shortens the gap between shipping a feature and documenting it.
The difference
What you own after the handover#what-you-own
The end state is a documentation stack your team can run without voix and without a vendor: Markdown in your Git account, a build you can execute locally, and a publishing pipeline your engineers can read and change.
- The repository
- Documentation ships as Markdown files with frontmatter in your own Git account, next to the config and build scripts that turn them into a site. voix keeps a copy of the initial delivered project for one year; after that it exists only where you host it.
- The deliverables
- On full payment the final deliverables are yours. voix keeps rights to its own pre-existing tools, templates and know-how, and publishes nothing about your project or your name without written consent.
- The bill
- One project fee, paid 50% at signing and 50% on delivery. No subscription and no per-seat charge from voix, and the stack you land on is open source, so there is no platform licence to renew.
Every engagement covers
- Content audit and migration map
- Information architecture redesign
- Docusaurus implementation
- Versioning and release workflow
- CI/CD publishing setup
- Search and navigation optimisation
- Authoring standards and templates
- Contributor onboarding and training
- Governance and ownership model
- QA, redirects and link checks
- Launch support and handoff playbook
- Post-launch iteration plan
Process
How a migration runs#how-it-works
Four phases, in order. Standard delivery is within two business weeks of the deposit and the materials we need, and the written proposal fixes scope, timeline and fees before the first file moves.
Restructure
We redesign the information architecture and the navigation model first, then convert content into Markdown with frontmatter, so structure is settled before files move.
Implement
We stand up Docusaurus in your repository and wire the delivery path: CI/CD publishing, redirects, link checks, search, templates and a quality baseline.
Hand over
We train the authors and reviewers, write down the governance model, and hand you the repository with a launch playbook and a post-launch iteration plan.
Questions
Common questions about documentation migration#common-questions
Short answers to the four questions that usually decide whether a migration happens.
How long does a documentation migration take?
Standard delivery is within two business weeks of receiving the deposit and the materials needed to start. Scope, timeline and fees are agreed in a written proposal before any work begins, and anything outside that scope is approved in writing rather than absorbed silently.
What does a documentation migration cost?
A migration is a one-time custom quote, scoped by documentation volume, complexity and implementation requirements. Payment is 50% at contract signing and 50% on delivery, with no subscription, no per-seat fee and no recurring platform licence.
Who owns the documentation after the migration?
You do. On full payment the final deliverables are yours and the content lives in your own Git account as Markdown files, while voix keeps rights only to its pre-existing tools, templates and know-how.
What happens to our existing documentation URLs?
They keep resolving. Redirects, QA and link checks are part of the delivery scope, so old paths point at their new pages and every internal link is verified before launch.
Tell us what you are locked into
Send the platform you are on, roughly how many pages you have, and what breaks today. You get back a scope, a timeline and a fixed quote.