Skip to main content
StringsOSFree beta
Documentation: Translation editorExpand nav
Back to all docs
Documentation

The core workspace for translators, reviewers, and engineers. Edit safely with statuses, QA signals, and recorded history.

Navigation

The core workspace where translators and reviewers collaborate. It features inline editing, quality assurance signals, translation memory matching, and strict status-driven approval workflows.

1Workspace
2Project
3Editor

Workspace

Inline & Focused Editing

Navigate seamlessly with your keyboard. View all keys in a table or focus on a single key for deep context.

Translation Statuses

Translations move through clear states: Untranslated, Draft, Needs Review, Approved, and Override.

AI & QA Panels

Review consent-based AI suggestions and available QA signals beside the translation input.

History & Restore

Every single edit, approval, or AI suggestion is tracked. Restore previous versions with one click.

Status-driven workflows

The Editor enforces a strict localization lifecycle. An AI suggestion starts as a Draft. Once a human touches it, it moves to Needs Review. Only authorized reviewers can mark it as Approved. If a developer edits a file directly in GitHub, the Editor detects it as an Override.

  • Untranslated
  • Draft
  • Needs Review
  • Approved
  • Override

Interface

The translation editor is where the bulk of localization work happens. It is designed to be highly keyboard-accessible, allowing you to rapidly move between fields without reaching for a mouse. The interface features a side-by-side view with the source string on the left, and the target input on the right, providing immediate context.

Workflow

Every string in StringsOS has a defined state. Untranslated means no work has started. Draft indicates initial work (often by AI). Needs Review signifies that a human translator has entered text, but it requires secondary approval. Finally, Approved means the string is ready for production. Override occurs if the translation was manually changed outside of StringsOS (like a direct GitHub commit).

Auditability

StringsOS acts as the ultimate source of truth. Every edit is tracked. If a translator makes a mistake, or a developer accidentally overwrites a key, you can view the complete version history of that key. With a single click, any previous version can be restored to the active state.

Next Steps

Learn how to organize the actual keys and namespaces you will be editing.

Keys and Namespaces

Jump into the Translation Editor and experience the difference.

Get started free
Book a demo

Free during beta · No credit card required