How It Works
PageTurner takes your documentation repository and delivers a fully translated, deployed, and maintained multilingual site. Here's what happens.
The Three Steps
1. You connect your repo
Point us to your documentation repository (or the docs path in a monorepo). Tell us which languages you want.
That's all we need from you.
2. We translate and deploy
PageTurner clones a mirror of your repo, translates the content, and deploys the translated site to Vercel. Each target language gets its own production URL.
3. Updates sync automatically
When your source documentation changes, our CI/CD pipeline detects the updates, retranslates only what changed, and redeploys. You don't need to trigger anything.
Translation Approach
PageTurner doesn't just translate sentences one by one. It analyzes your entire documentation first to understand the domain, extract technical terminology, and build a consistency dictionary. Then it translates with that context enforced across every page.
This is why "repository" doesn't become three different words on three different pages.
What gets translated:
- Markdown and MDX text content
- Navigation labels and sidebars
- Configuration strings and metadata
What stays untouched:
- Code blocks and inline code
- React/JSX component structure
- Import statements
- Links and file references
Translation Quality
Based on 19 production deployments across 13+ languages:
| Metric | PageTurner | Generic Translation Tools |
|---|---|---|
| Term Consistency | 99%+ | ~70% |
| Technical Accuracy | 94% | ~68% |
| Structure Preservation | 100% | ~65% |
| Overall Quality | 91/100 | 65–70/100 |
Real examples
- Prettier (7 languages) — browse the live demo
- Redux (6 languages) — browse the live demo
- Jest (7 languages) — browse the live demo
All 19 demos are available on the dashboard.
How Updates Work
PageTurner uses translation memory to track what's been translated. When your source docs change:
- Change detection — identifies which pages were modified
- Selective retranslation — only changed content gets retranslated
- Automatic redeployment — updated site goes live
Cost impact: Updates typically cost 60–80% less than the initial translation because unchanged content is reused.
Compared to Alternatives
| PageTurner | Human Translation | Generic MT | |
|---|---|---|---|
| Time to deploy | Hours | Weeks | Hours |
| Cost (100 pages, 3 langs) | ~$30 | $3,000+ | ~$20 |
| Term consistency | 99%+ | 95–100% | ~70% |
| Quality | 91/100 | 95–98/100 | 65–70/100 |
| Component preservation | Automatic | Manual effort | Breaks components |
| Ongoing maintenance | Automatic CI/CD | Manual re-engagement | Manual |
PageTurner hits the sweet spot: near-human quality at a fraction of the cost, with maintenance built in.
Next Steps
- Getting Started — How to onboard
- FAQ — Common questions
- View live demos — See it in action