Build it with your agent

Two conversations as they could go: you say one sentence, your agent builds on i18next, and the texts end up in plain files in your repo.

Skip to your own case
YouTue 09:12

Make my bakery’s website available in German and French.

Your agent09:15

Done. I used i18next, an open-source library for translations: every text now lives in one plain file per language, not inside the pages.

  1. Moved 38 texts out of the pages into locales/en/common.json
  2. Wrote locales/de/common.json and locales/fr/common.json
  3. One address per language, /en/ /de/ /fr/, with hreflang links between them
  4. A language switcher in the header
  5. Ran i18next-cli status: no text is missing in any language

Worked for 3 minutes · 14 files changed

Here is the home page. Try the switcher, or change the number of loaves: French puts 0 in the singular, English and German in the plural.

Before · English only
kornfeld-bakery.com/
After · in three languages
kornfeld-bakery.com/de/

The previews run i18next in this page, with the translation files your agent wrote.

A week later
YouMon 17:40

Can our shop assistant reword the French tagline herself? She is from France.

Your agent17:40

Yes. It is one line of locales/fr/common.json. She can change it there, on GitHub or in any editor, or ask any agent to do it. If she would rather not touch files, a translation management tool can sit on top of the same files.

locales/fr/common.json
{
  "tagline": "Pain au levain et viennoiseries, cuits chaque matin.",
  "loaves_one": "{{count}} pain de seigle pour demain",
  "loaves_other": "{{count}} pains de seigle pour demain"
}

Writing the code yourself, or checking what your agent wrote? The docs