Pages
Translating
The app's own text is translated by Claude Code, into files in the repository that you review. What people post is translated by Workers AI as it's posted. Here is each, with the lines that do it.
This app's catalogs
| i18n/translations/ar-EG.json | 361 of 361 strings translated |
| i18n/translations/th-TH.json | 361 of 361 strings translated |
The events are translated by Workers AI: see them.
Built into Vite+
Translation isn't a separate tool: it's part of each command a Vite+ app already runs, the same on your machine as in CI.
vp exec void-fbtee initpackage.json (void-fbtee)- Once: sets the app up. void-fbtee's only command.
vp devvite.config.ts (voidFbtee)- As you save, adds new strings to every language, marked new, and Claude Code or Void's AI translates them; the dev server reports what's left. An edited translation shows at once.
vp buildvite.config.ts (voidFbtee)- Fails on anything left: an untranslated string or page, a page older than its original, a setup problem. So a deploy can't ship one.
vp checkvite.config.ts- Lints with fbtee's own rules: text nobody wrapped for translation is an error.
CI.github/workflows/ci.yml- Runs the same commands on every push: check, build, then deploys and checks the live site.
How it's done
vp dev translates, with Void's AI or Claude Code
There's nothing to run. As you save, vp dev adds each new string to every language's catalog and translates what's new, the strings and the markdown pages that changed: with Claude Code and void-fbtee's skill when it's on your machine, else with Void's AI, in the app's own Worker, when the app uses it. What people post is translated by Void's AI.
voidFbtee({ sourceLocale, locales, site: SITE, common }),import { translate as translateText } from "void-fbtee/ai";- Translating is part of the dev server: `vp dev` prepares each new string, translates what's new as you save, and reports what's left. `vp build` fails on anything left. There are no i18n scripts.Files you review
The translations are files in the repository, one catalog per language and a copy of each markdown page, so they're reviewed with git diff and committed like code. Nothing is translated while a visitor waits.
"status": "translated",What people post, as it's posted
An event someone posts isn't in the repository, so it's translated as it's posted: the post goes to a queue, and its consumer asks Workers AI for each of the app's other languages, after the poster has their answer.
await queues.translate.send({ eventId: created.id });const MODEL = "@cf/meta/llama-3.3-70b-instruct-fp8-fast";The full reference is in void-fbtee's skill.