Translations
Getting started
Scan, draft, publish — translated copy live worldwide in five minutes.
▶
Translations in 5 minutes
~5 minutes01 · INSTALL
Add the SDK and CLI
Same SDK + CLI as flags. No separate i18n package, no separate API key.
$npm i @shipeasy/sdk && npm i -g @shipeasy/cli
02 · WIRE
One configure call
Same shipeasy() boot as flags. Import i18n from the same package to read labels — i18n.t(key, fallback).
$// app/layout.tsx
import { shipeasy } from '@shipeasy/sdk/server';
await shipeasy({ serverKey: process.env.SHIPEASY_SERVER_KEY ?? '' });
03 · SCAN
Discover strings in your repo
Walks your code, finds untranslated user-facing copy, proposes keys, and uploads them as drafts.
$shipeasy i18n scan ./apps/web
04 · TRANSLATE
AI drafts → human review
Drafts ride through the review queue in the dashboard. Approve and publish when you're happy.
$In the dashboard: Drafts → AI draft (or run the i18n_translate_draft MCP tool)
05 · USE
Render in your app
Reads happen at the edge. New keys live within a second of publish.
$import { i18n } from '@shipeasy/sdk/server';
<h1>{i18n.t('home.hero.title', 'Localize easily.')}</h1>
Where to next
ConceptKeys & namespaces
How keys are structured, namespaced, and resolved.
Read →ConceptDrafts & reviewHow AI translations move through review and publish.
Read →ReferenceProfilesPer-locale tone, glossary, voice — applied to every AI draft.
Read →ReferenceCLI commandsEvery shipeasy i18n … verb the CLI exposes.