Skip to main content
Choose a workflow based on where your content lives and how often it changes. Each path ends with review and delivery.

​
For your first batch

Follow Your first translation. Use a small source file and one target language so you can inspect the entire result. Add terminology and tone guidance before requesting more work.

​
For recurring content

Test a manual cycle first. Then configure an automation for the project and trigger you need. Avoid submitting a manual request for a batch already handled by a source-upload automation. Content sync moves repository content. Check its configured direction and behavior rather than assuming that connecting GitHub also starts translation.

​
For existing translations

Import target files against their matching native source files. Imported translations are marked approved, so verify them before importing. To reuse sentence pairs across content instead, import a translation memory. For offline review, export a filtered queue. That export does not automatically apply later edits or approvals back to Platform.

​
Agree on the review gate

Generation success means the job completed. Before delivery, check untranslated strings, quality issues, and the agreed review scope. Use roles and permissions to assign approval responsibilities.

​
Next

Start a translation, track the job, and review the result.