About
voix moves product documentation off locked proprietary platforms onto an open-source stack the client owns: Markdown in Git, a static site, a publishing pipeline that runs in CI. It is run by Maria Gilca, a documentation architect based in Moldova, and it works remotely with teams anywhere.
Maria Gilca, documentation architect. She scopes the work and leads the engagement.
Moldova, inside an IT park. Clients are remote, and so is the work.
One-time projects under a written proposal. No retainer, no subscription, no licence.
The person behind it
voix is run by Maria Gilca, a documentation architect based in Moldova. She founded the studio, scopes each engagement, and stays on it from the first content audit through to the handoff session where your team publishes without her.
Documentation architect is not a title most companies have on the org chart, which is roughly the problem. Two roles usually share the work and neither owns it: the technical writer, who knows how to explain the product, and the platform engineer, who knows how to build and ship a site. The layer between them is unclaimed — what counts as a page, where it lives, who reviews it, how it reaches production, and what happens to all of it when the product changes shape. That layer is what voix is hired for.
The engagements look alike more often than not. Documentation starts wherever it was easiest to start — a hosted help centre, a wiki, a folder of shared documents, a README that kept growing — and by the time anyone treats it as a system there are four systems. Search returns three versions of the same page, two of them wrong, and nobody can say which one is canonical because nothing in the setup ever forced that question. A migration is the moment the question finally gets asked, page by page, with someone accountable for the answer.
The positions taken on this site are hers: that documentation belongs in the same repository as the product it describes; that reviewing a docs change should look like reviewing a code change; that a platform you cannot leave is a platform you do not own; and that an engagement should end with your team shipping on its own. None of those are neutral. A studio holding the opposite views would build you a different site and sell you a different contract.
There is no client list on this page and no logo strip. voix does not publish a client’s name or their work without written consent — that is written into the confidentiality policy and it rules out most of what a studio page normally uses as proof. What stands in its place is the method, stated in enough detail to be argued with: the services page says what is delivered and what is refused, the pricing page says what it costs and on what terms, the case studies are labelled composites rather than dressed-up client stories, and the field notes show the reasoning in public before you have paid for any of it.
Point of view
Documentation is the one part of a product that companies routinely agree to keep on someone else's platform, in someone else's format, behind someone else's export button. voix exists to undo that decision and to make the next one reversible.
The trade looks sensible when it is made. A hosted documentation platform gets a team publishing in an afternoon: a visual editor, hosted search, a theme somebody else maintains, no engineering time to beg for. Against a launch date that is a good deal, and it is usually the right call at the time. The cost arrives later, and it never arrives as a line on the invoice.
None of this is an argument for building your own tooling. The alternative is duller than that: Markdown files in the repository the product already lives in, a static site generator, and a pipeline in CI that builds and publishes on merge. Docusaurus, Git and Markdown are the usual answer here because they are open source, well documented, widely known, and boring in the way infrastructure should be — and because every part of the stack can be swapped, including the studio that assembled it.
That is the test worth applying to any documentation setup, including the one voix builds for you. Could you leave it? If the content is plain text in files, the history is in your own Git account, and the site builds with a public tool your engineers already understand, then the platform is a choice you keep making rather than one you made once and now pay for annually. Lock-in is not really about price. It is about how much of your documentation strategy has to be negotiated with a vendor before it can be discussed with your readers.
The commercial model follows the same argument, because it would be incoherent otherwise. voix charges a one-time project fee: a studio living off a retainer has a permanent incentive to leave you needing it, and that incentive eventually shows up in the work. The engagement is designed to finish. What is on the pricing page is the entire commercial relationship — a fee, a deposit, a delivery window, and an optional maintenance package if your team wants a safety net while it takes over.
Principles
Five rules decide how an engagement runs. They apply whether a project is twelve pages or twelve hundred, and each one costs voix something — which is the only reason to believe they are real.
A migration is a project with an end. It runs under a written proposal that fixes scope, timeline and fee: 50% is due at signing, 50% on delivery, and standard delivery is within two business weeks of the deposit and the materials the work depends on. Nothing renews afterwards. If your team never needs voix again, the engagement did what it was for.
The documentation lives in your Git account, in your organisation, from the first commit rather than at handoff. On full payment you own the final deliverables; voix keeps rights only to its own pre-existing tools, templates and know-how. A copy of the initial delivered project is kept for one year, and after that the project lives entirely on your hosting.
Content is Markdown. Metadata is frontmatter. Navigation is a file in the repository. History is Git history. Nothing that matters is stored in a format a single tool can read, and nothing critical depends on an account only voix can sign into. The test is blunt: you should be able to move the whole site again, to something else entirely, without asking permission.
Authoring standards, page templates, a contributor guide and hands-on onboarding are part of delivery, not an upsell bolted on at the end. The real measure of a finished migration is the first release note your team publishes without asking voix anything, and the handoff playbook exists so the second one is easier than the first.
Anything outside the agreed scope needs written approval before it is built, so the fee never moves quietly. That cuts both ways: if a request would make the documentation harder to maintain, or belongs in a tool you already pay for, you get told that instead of getting a quote for it.
These are principles, not the agreement. The terms and conditions set out payment, defects, ownership, liability and governing law in full, and the confidentiality policy covers how your material is handled while the work runs and what happens to it afterwards. Read those two for the commitments; this page is only the reasoning behind them.
If you want the same principles expressed as deliverables rather than positions, the services page breaks the engagement into what gets built, the process page puts the phases in order and says who does what in each of them, and the FAQ answers the objections that usually come before a first email.
Location and contact
voix is based in Moldova, inside an IT park, and works remotely with teams anywhere. Engagements run asynchronously and in writing, with scheduled calls for kickoff, training and handoff.
The park is a cluster of small product companies and studios, which turns out to be a useful place to run this kind of work from. The people around us are building the products that will need documentation in a year, so the failure modes show up early and in person: the wiki nobody prunes, the help centre that two teams edit and neither owns, the API reference that drifts a release behind the API.
Remote is the default rather than a concession. Most of a migration is written work reviewed in pull requests — a migration map, an information architecture, converted pages, a publishing pipeline, a set of templates — and a pull request reads the same whether the reviewer is in the next room or six time zones away. Moldova sits in Eastern European time, which overlaps a full working day with Europe and the start of the day in North America.
The first step is an email, and it goes to the person who would do the work. Describe what you have, where it lives today and roughly how many pages are involved, and you get back either a scope conversation or a straight answer about why voix is not the right fit for it. The pricing page lists what to include if you want a fee estimate in the first reply rather than a second round of questions.
No account manager and no discovery funnel. Describe your documentation and where it lives today, and you get a written scope back.