First steps
Do I need a developer to set transglot up?
Only if you want strings to flow from your codebase. Uploading files, migrating from another tool and connecting a content platform need no code.
There are three ways to get strings into transglot, and they need very different amounts of engineering.
| Route | Who sets it up | Plan |
|---|---|---|
| Upload or migrate. Upload language files, a zipped locale folder, or bring a project across from Lokalise, Phrase, Crowdin, Transifex, Weblate or POEditor. | Uploading: a developer, admin or account Owner. Migrating: an admin or account Owner, with a read token from the tool you are leaving. No code either way. | Every plan |
| Connect a system you already run. A code repository, a content platform or a file-storage service, set up once from the integrations screens. | An admin, plus someone with access to the other system to authorise the connection. This is configuration, not programming. | Starter and up |
| Push from your codebase. The CLI, the GitHub Action or the API, fitted into your existing build. | A developer. | Starter and up |
Getting translations back out has the same split. Exporting files and publishing back to a connected content platform need no code. The CDN needs a few lines in your app. A connected repository opens a pull request against your own files with no change to your app at all.
Where to start
- No code: Import content or Import from another tool.
- Connect a system: Connect GitHub, Connect a content platform or Connect file storage.
- From your codebase: the Quickstart.
See Plan requirements for what each integration needs.