FAQ
Straight answers about what a documentation migration costs, how long it takes, what your team has to do, and who owns the result. Every answer here is the one you would get on a call.
Two business weeks from the deposit and the materials, for the scope in the signed proposal.
A one-time custom quote. No subscription, no per-seat fee, no platform licence.
You own the content and the deliverables in full once the project is paid.
Getting started
The basics, for anyone arriving here from a search result rather than from a sales conversation.
voix is a documentation-migration studio that moves product documentation off locked proprietary platforms onto open-source stacks your company owns: Docusaurus, Git, Markdown and CI/CD. The work covers four areas — consolidation and information architecture, modern platform implementation, employee onboarding and enablement, and CI/CD documentation delivery. The services page describes each one in depth.
voix works with product, platform, support and enablement teams at scaleups that are paying for a documentation platform they cannot leave. The usual reason to get in touch is a renewal quote nobody wants to sign, an export that produces unusable HTML, or a documentation set that has outgrown the tool it was started in. Company size matters less than whether the content is trapped.
The first conversation maps where your documentation lives today, how much of it there is, who writes it, and what has to be true on launch day. That becomes a written proposal or statement of work naming the scope, the timeline and the fee before any work starts. Nothing is billed until it is signed. The process page sets out the phases that follow.
voix is a studio founded and run by Maria Gilca, a documentation architect based in Moldova and working remotely with clients anywhere. Specialist collaborators join when a project needs them, and access to your material is limited to the people delivering the work. You talk to the person doing the migration rather than to an account manager. More about the studio.
Scope and timing
Timing, deliverables, and the parts of the work that need someone on your side.
Standard delivery is within two business weeks of voix receiving the deposit and the required materials. That window applies to the scope agreed in the signed proposal; a larger content set, a more complex information architecture or extra implementation work is quoted with its own timeline. The clock starts when the deposit and the materials arrive, not at first contact.
A migration engagement covers the 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, a governance and ownership model, QA with redirects and link checks, launch support with a handoff playbook, and a post-launch iteration plan. Each area is described on the services page.
voix needs access to your current documentation, the exports or credentials named in the proposal, and one person who can approve information architecture decisions. The authors who will maintain the docs afterwards need to be available for the onboarding sessions. Everything else — content cleanup, implementation, redirects, pipeline setup — sits with voix unless the proposal says otherwise.
Old URLs are mapped to their new locations and shipped as redirects, so existing links, bookmarks and search results keep working after launch. Redirect mapping, QA and link checks are part of every migration rather than an add-on. Where a page is merged or retired, its redirect points at the closest surviving page instead of dumping the reader on the home page.
Platform and ownership
The questions that decide whether this migration is the last one you have to pay for.
An open-source stack removes the exit cost. Your documentation becomes Markdown in a Git repository you control, so changing hosts, themes or tools later is a normal engineering task rather than a renegotiation. Proprietary platforms keep the content in their own format, and their export usually returns the wrapper HTML from the editor instead of clean source you can reuse.
Docusaurus is the default because it is open source, reads Markdown and MDX, ships versioning and internationalisation, builds to static files with no server to run, and any React developer on your team can already read it. This site runs on it. If a different open-source generator fits your stack better, that is a scoping conversation rather than a refusal.
You own the content and the final deliverables in full once the project is paid. voix keeps rights only to its own pre-existing tools, templates and know-how, which are reusable across clients and are never a licence you have to keep paying for. The finished project lives in your own Git account or hosting, not behind a voix login.
Yes. A Docusaurus build is a folder of static HTML, CSS and JavaScript, so it runs on your own servers, on an internal network, or on any static host such as GitHub Pages, Netlify or Cloudflare Pages. There is no voix-hosted component and no platform licence, so the only running cost is whatever your chosen host charges, billed directly to you.
You keep everything, and nothing stops working. The documentation is Markdown in your repository, the publishing pipeline is standard CI/CD configuration, and the platform is open source, so another team or another vendor can pick it up without an export request or a second migration project. Handoff is built for exactly that: templates, authoring standards and a written playbook ship with the site.
Cost and terms
Pricing is a custom quote, but the shape of the agreement is the same every time.
A documentation migration is a custom quote: a one-time fee scoped by documentation volume, complexity and implementation requirements. There is no subscription, no per-seat fee and no recurring platform licence, so the cost stops when the project ships. The pricing page sets out what the fee covers and how a quote is put together.
Payment is split in two: 50% deposit at contract signing and 50% on delivery. Delivery runs to the scope in the signed proposal, and standard turnaround is two business weeks from the deposit and the materials arriving. Late payment carries a 5% daily fee, and out-of-scope requests are only picked up once they are approved in writing.
The 5 interventions package is an optional add-on covering five post-launch maintenance interventions for fixes and minor documentation updates, at a small extra cost on top of the migration fee. It exists for teams who want a safety net during the first weeks of running the site themselves. It is not a retainer and not a support subscription.
Bugs that voix introduced are fixed at no charge. Defects caused by changes your team made after handoff are quoted case by case and capped at 500 EUR, so there is a ceiling on the surprise. Anything that is new work rather than a fix goes through the out-of-scope route: a written estimate first, your written approval second.
After launch
A migration only works if the team can keep publishing without calling anyone.
Your team maintains it, which is the entire point of the handoff. Authors write Markdown, open a pull request, get a review, and the pipeline publishes. The governance model that ships with the site names who owns each section, who reviews changes and what the quality baseline is, so maintenance is a defined job rather than whoever happens to remember.
Training is hands-on with your own content: authors learn the editing workflow, the templates, the review step and the publishing pipeline by shipping real pages. Contributor onboarding is part of every migration rather than an extra, and the migration handbook documents the same workflow so people who join later can get up to speed on their own.
voix retains a copy of the initial delivered project for one year, after which the project lives on your Git account or your own hosting. Confidential material is used only to deliver the services, and access is limited to collaborators who need it. voix publishes neither your name nor your project without written consent, and returns or deletes materials on request.
Nothing on this page is a hidden term. The commercial answers come from the terms and conditions and the confidentiality policy; the delivery answers come from the process and the services. If the question you need answered is missing, send it and it gets added here.
Send your current platform and roughly how many pages you have. You get back a written scope, a timeline and a fee.