The deploy screen answers one question (is this locale ready to ship?) and gives you the copy-paste snippets to ship it.
Who this is for
Whoever gets translations out of transglot and into your product. Publishing itself needs admin.
What happens next
Locale readiness lists each target language against the project's source strings, with the runtime version it currently serves: either a version number or never published. The bar shows translated against total, with flagged strings marked separately.
Below that is the focus card, and it says one of two things. When a locale is complete it reads Ready to ship and offers Publish for that language, telling you which version number is next. When nothing is complete it reads Not ready yet (either "No target languages yet" or "Every target locale still has untranslated strings. Publishing now would ship gaps to production.") and links you to where to fix that.
Deploy history is the append-only log of published runtime versions, with absolute timestamps because it is a ledger, not a feed.
The rest of the page is the copy-paste half, "pre-filled with this project's real URL and credentials": Connect & verify, Command line (CLI), a GitHub Action workflow file, In-context editing, and Tokens, keys, webhooks & CDN, plus Token usage.
If it doesn't work
"No runtime versions published yet.": nothing has been published from this project.
"An organisation admin publishes runtime versions.": you can see readiness but not publish.
If publishing is not on your plan, the page says so rather than offering a button that would fail. Readiness, the deploy log and every snippet on the page work on every plan.
Related
Publish a locale
The CDN
Create a deploy token