πŸ“ Setting up a project

Organize translations, track history, and maintain locales over time.

Projects

Projects open the door to a full localization feature set and allow you to better manage your translations over time.

Creating a project

There are two ways to create a project:

From a translation job

After completing a Quick Translate, you can convert the results into a project. This uses the source and translated files from that job as the starting point.

Manually

Manually creating a project is an option if you already have existing translations that you want to import.

You'll need to:

  1. Give the project a name
  2. Upload your source JSON
  3. Add target languages (either pick from the dropdown to start fresh, or upload your existing translated JSON files)

If you upload existing translations, JTranslate will detect the language, and once you confirm project creation it will check them against your source. This will show you what's missing or outdated so you know what work is required to bring them all up to date.

What's an alias?

Each target language has an alias, which is the filename used when downloading or syncing via the CLI. By default, it matches the language code (e.g. fr for French), but you can change it to whatever you need.

Language aliases must be unique, just like file names.

How it all works in a nutshell

Once you have a project set up:

  1. You update your source file whenever you make changes to it, either via manually uploading within the web app or through the push command in the CLI.
  2. JTranslate detects changes by comparing it to the previous source version. Identifying your added, modified and removed keys.
  3. You can then perform a project quick translation to bring your target languages up to date with the source.
Deleted projects are archived for 7 days before being permanently removed along with all locale files and history.