Sign inSign up
For technical writers

Docs that translate on every pull request.

Keep eleven languages of documentation in lockstep with the source — without ever leaving your repo. Rush Studio watches your docs branch, drafts every changed segment with AI, and routes it to a reviewer who actually sees the context.

Markdown · MDX · reSTGitHub · GitLab · BitbucketStructured TM
github.com/acme/docs/pull/2418
docs / quickstart-rewriteopen
Rewrite the quickstart for the v4 SDK
#2418 · opened by rachel-p · 3 commits · changes +24 −7
docs/quickstart.mdx+9 −2
12−Install the SDK with npm i @acme/sdk then call start().
12+Install the SDK with npm i @acme/sdk@4 and call boot() from your entry file.
13+A boot call now returns a Promise so you can await the handshake.
Rrush-studio bot · drafted translations in 11 languages12s ago
DEapproved
Installiere das SDK mit npm i @acme/sdk@4 und rufe boot() aus deiner Einstiegsdatei auf.
FRreview
Installez le SDK avec npm i @acme/sdk@4 et appelez boot() depuis votre fichier d'entrée.
JAreview
npm i @acme/sdk@4 で SDK をインストールし、エントリファイルから boot() を呼び出します。
ESdraft
Instala el SDK con npm i @acme/sdk@4 y llama a boot() desde tu archivo de entrada.
11
languages, parity on launch day
<1h
from merged PR to translated locale
94%
TM reuse across releases
The docs localization tax

Three things that keep translated docs perpetually behind — and the feature that ends each one.

The problem

Docs ship in English, then sit in the localization backlog for weeks. Every release widens the gap between the English source and every other locale.

The feature that fixes it
Automations→

Every merged PR fires an automatic draft in all your target locales. Reviewers get the diff — not a re-export — so translated docs land in the same release, not the one after next.

Trigger12s ago
docs/quickstart merged to mainMerged
DESchnellstart aktualisiert
FRDémarrage rapide mis à jour
JAクイックスタートを更新
ESInicio rápido actualizado
The problem

Reviewers translate a bare string with no idea which page, callout, or code block it belongs to — so technically-correct translations still read wrong on the rendered page.

The feature that fixes it
In-context preview→

The editor renders the doc the way readers will — sidebar, callouts, syntax highlighting — with the segment highlighted in place. Reviewers translate against the real surface.

Reviewer sees the rendered page
FR · in review
Docs / Guides / Quickstart
Installez le SDK

Ajoutez le paquet, puis appelez boot() depuis votre fichier d'entrée.

$ npm i @acme/sdk@4
FR
The problem

A single release breaks terminology across every locale: the CLI flag, the API object, the product name all drift the moment a new translator touches them.

The feature that fixes it
Glossary→

A docs-grade glossary locks product names, CLI flags, and API objects. Anything off-glossary is flagged while the translator is still typing — never at build time.

Locked terms · enforced at draft time
Rush Studio→Rush Studio
workspace→espace de travail
boot()→boot()
« Espace Travail »≠off-glossary · flagged
Round-trips your source

Your files come back exactly as they left.

Frontmatter, JSX components, code fences, tables, and admonitions survive the round trip with formatting intact. No re-tagging, no broken builds.

MarkdownMDX & JSXreStructuredTextAsciiDocCode fencesFrontmatterCallouts / admonitionsTables
Workflow

How it works for technical writers.

1

Connect the docs repo

Point Rush Studio at the branch your docs live on. We watch every PR.

2

AI drafts the changed segments

Only the changed lines — TM fills the rest. Drafts land in minutes, not days.

3

Reviewers approve in context

Each segment shows the rendered page, the prev/next paragraphs, and any screenshots.

4

Push back to the repo

Translated MDX commits back as locale folders. Your site builds them like any other branch.

Standard on every plan

Plus the foundation every team runs on.

The docs-specific workflow rides on the same foundation every Rush Studio team gets:

Translation memory
Every approved segment is reused the next time it appears — across files, projects, and quarters. You never pay to translate the same sentence twice.
Learn more
Brand voice
Tone, register, and do-not-translate rules travel with every project so the AI drafts — and reviewers approve — in your voice, not a generic one.
Learn more
AI quality scoring
Every draft is scored and risky segments are flagged before a human opens them, so reviewers spend their time where it actually matters.
Learn more
Glossary
Product names, UI terms, and legal phrasing are locked. Anything off-glossary is flagged at draft time — long before it can ship inconsistent.
Learn more
"Our docs repo is the source of truth. Rush Studio's GitHub integration translates every PR diff in 9 languages before the original ships. We stopped having a localization backlog."
RP
Rachel Park
Documentation Lead · Orbital
MarkdownGitHubAPI docsSDK referencesRelease notes
Other roles

Built for the rest of your team too.

Marketing teams
Campaigns shipped in every market
→
Localization managers
Run the whole pipeline from one screen
→
Product managers
UI strings, in-app copy, release notes
→
Design ops
Figma frames into 22 languages
→

See Rush Studio in your stack.

Join the waitlist and our team will help you set up a project from your own files — usually in under a week.