Setup steps

Setup steps is one list that you see at two scopes. On your dashboard, the card labelled Across your workspaces covers every project you can reach. On a project's Get started page, the card labelled This project covers that project only.

The five stepsCopy Anchor Link

Steps the project already satisfies count from the start, such as target languages you picked while creating it, or a teammate already in the workspace. Progress is worked out from your real state each time a page loads, so finishing a step anywhere updates every place the list appears, and doing steps out of order works as well as doing them in order.

Reading the cardCopy Anchor Link

• The card counts N of M complete beside its title, with a bar of the same figures.
• The next step in order is highlighted. An unfinished step carries a link named for what it does: Create a project, Add a language, Add strings, Open the editor or Invite someone.
• A step you are already on reads "You are on the page for this step."
• A step your role cannot do names who does it instead of linking you to a screen that would refuse you. A translator, for example, reads "Someone who can manage the project’s languages does this step." under Add a target language.
• On the dashboard, finished steps are folded behind N already done so what is left comes first.
• When every step is done, the card says so and stays finished, even while strings are waiting to be translated.

Bringing strings in from the Get started pageCopy Anchor Link

Below the setup steps, a project's Get started page offers two ways to add your source strings:

• Upload your language files takes JSON, YAML, XLIFF, .strings, .arb, .po and more, straight from your machine. Nothing is written until you confirm what was detected.
• Push from your codebase gives ready-made snippets for transglot.json, the command line and curl. Pick a framework preset and the snippets rewrite themselves for it, with your project's details filled in. If you can manage tokens, select Generate deploy token to fill the snippets with a real token. It is shown once: "Deploy token minted. Copy it now, it is shown once."

The CLI, the GitHub Action and the API need a deploy token, which starts on the Starter plan. On Free, the page says so, and uploading works instead. See Deploy tokens.

Try a sample firstCopy Anchor Link

Seed a sample project on the Get started page, or Explore a sample on the dashboard, creates a finished project with real strings so you can look around before wiring up your own. It is a real project, so you need to be allowed to create projects, and your plan needs room for one more. When it is not available, the dashboard shows why: Needs a spare project when the account has no room for another project, or Admins and owners when your role cannot create projects.

If it doesn't workCopy Anchor Link

• A step you finished still reads as not done. It is usually Run your first translation: a run that has not written any translation yet does not count. Open the editor, translate the missing strings again, and the step ticks once something lands.
• There is no token strip. Either your plan does not include API access, in which case the page says so and you upload files instead, or your role cannot create deploy tokens in this project. Ask an admin.
• You see no setup card on the dashboard. If you were given access to specific projects rather than a whole workspace and none of them has strings yet, the dashboard does not show the account-wide card, because its steps are work for whoever runs the workspace.

RelatedCopy Anchor Link

• Your dashboard
• Translate with AI
• The command line tool