Help centre
How to do things inside locoloop, in the order you will need them. Everything here is a page you can follow end to end — nothing on this site describes a feature that does not exist.
Get started
In order. About an hour from an empty workspace to translations in your build.
- 1Create a workspace and a platformA platform is one app: its key namespace, its file format, its languages. How platforms and projects fit together.
- 2Import your English fileDrag it in. The format is detected from the file, nested keys keep their path, and anything unreadable is reported rather than skipped. The ten formats.
- 3Set the glossary and the registerDo this before the first translation pass, not after. Glossary and context · Formality registers.
- 4Translate, then have a human approveAI drafts arrive flagged for review. Reviewers are free, so the colleague who speaks the language costs nothing to invite. Roles and permissions.
- 5Wire it into your buildOne push job, one pull job, and a status check that gates the release. All integrations.
Connect your pipeline
A workflow that pushes on merge and opens a pull request with the translations.
GitLab CITwo jobs and a masked variable.
Bitbucket PipelinesOne shared step, one secured variable.
REST APIPush, pull and status, with scoped keys and ETag caching.
MCP serverSix tools that give a coding agent the string set.
File formatsWhat each format round-trips, and how plurals are held.
Reference
Plurals, formats, translation memory, data residency, and how to export everything.
GuidesThe background reading: plural rules, formal and informal address, continuous localization.
SecurityHashing, session handling, tenant isolation and encryption at rest.
Data processingRoles, sub-processors and the DPA.
Follow the first walkthrough with a real workspace open
Creating one takes a minute, and the first import takes one drag.