Setup
Project Settings and Locale Setup
Configure the project slug, language setup, permissions, and the settings screens your team will use most often.
The Settings area is where you define the boundaries of the project before any translation work starts.
General
Use Settings > General for the project slug and basic project identity.
Source and target locales
The project needs:
- one
source locale - one or more
target locales
The source locale is the language your team writes in first. In most projects that is English, but it does not have to be.
Target locales are the languages Inverb is allowed to translate into.
Important locale rule
The source locale should not also appear in the target locale list. If the source is en, then en should not be a target.
That rule matters because translated content belongs in localized fields, not back in the source fields your team authors directly.
Users and permissions
Use Settings > Users to invite teammates and manage access.
Translator users can also be scoped to specific target locales. That is useful when a person should only review or work on a subset of languages.
API keys
Use Settings > API keys when you need machine access to the app.
Keep API keys separate from CMS credentials and rotate them if they are no longer needed.
Recommended setup order
- Confirm the project slug.
- Set the source locale.
- Add target locales.
- Invite the right people.
- Connect Contentful.
- Configure AI models and glossary.