How to use Translation Manager

1. Create an account

Go to the app, open Sign Up, and enter your full name, email, and password (minimum 6 characters). After you create an account, use Login with the same email and password. Sessions are stored in your browser so you stay signed in on that device until you log out.

2. Create and open projects

The dashboard lists every project you own or were added to. Click New Project, set a name (for example your product name) and an optional description. Click a project card to open it. Each card shows how many languages and members it has.

3. Add languages

Translations cannot start until at least one language exists. The owner adds a language code (lowercase, such as en) and a language name (such as English). Add more languages later from the Settings tab. Only the owner can add or delete languages. Deleting a language removes all values for that language in the project.

4. Import a translation file

Owners and developers see Import on the Translations tab. Choose the target language, then upload a .json or .js file that uses module.exports. Nested objects are flattened with dot notation (for example nav.home).

Click Analyze File. You will see counts for new keys, unchanged values, and conflicts. For each conflict, pick Keep Existing or Use Imported, or apply Keep All Existing / Accept All Imported. Nothing is written until you click apply. If values already match, you can still apply to keep the key order from the uploaded file.

5. Edit keys in the grid

The Translations tab is a table of keys across languages. Search by key name. Filter to one language if the table is wide. On desktop, click a cell to edit; save with the check button or Ctrl/Cmd+Enter, or press Escape to cancel. On mobile, each key is a card with an Edit button per language.

Owners and developers can Add Key and enter the key plus a value for each language. They can also delete a key. QA can only update values on keys that already exist.

6. Keep interpolation placeholders

Strings often include tokens like {name} or {count}. If the original value has those curly-brace keys, a save is rejected if you remove them or rename them. You may change surrounding copy and reorder the tokens, but the names inside the braces must stay the same so your UI code still interpolates correctly.

7. Add users and roles

Open the Members tab. The owner uses Add Member with the person's email. That person must already be registered. Choose a role:

• Owner — you, the project creator: languages, keys, members, and deleting the project.
• Developer — add, update, and delete keys; import files. Cannot add languages or manage members.
• QA — update existing translations only. Use this for QA or a product owner who should correct phrasing without changing the key set.
• Read-only — view only.

The owner can change a member's role or remove them later. After they log in, the project appears on their dashboard.

8. Export and use the files in your app

In the project header, open Export. Download one language as {code}.json (for example en.json), or choose Export All Languages to download every locale. You can also export a single language from Settings. Copy the JSON into your i18n folder and deploy as usual.

9. History, restore, and settings

Each key has a history icon showing created, value set, updated, deleted, and restored events, including who made the change. Deleted Keys lists soft-deleted keys; owners and developers can restore them. Settings is where owners manage languages and, if needed, delete the entire project (this cannot be undone).