i18n

Loop ships translated into English, Spanish, French, and Portuguese — and adding a locale is straightforward.

Two layers of translation

Loop splits localization into two concerns:

• UI chrome (nav labels, buttons, breadcrumbs) is handled by next-intl with message catalogs.
• Content (headlines, features, pricing copy) lives in siteConfig as localized field siblings.

This split keeps marketing copy editable in one config file while letting the framework handle the plumbing.

URL-prefixed routing

Routes are prefixed with the active locale, e.g. /en/docs, /es/precios. The middleware.ts at the project root negotiates the locale and the [locale] segment carries it through every page.

src/app/[locale]/docs/page.tsx
src/app/[locale]/pricing/page.tsx

Content fields

Localized content uses suffix conventions throughout siteConfig:

{
  title: "Pricing",
  titleEs: "Precios",
  titleFr: "Tarifs",
  titlePt: "Preços",
}

A small helper reads the right field for the active language and falls back to English when a translation is missing, so partial translations are safe.

Add a new locale

1. Add the locale code to the locales array in src/i18n/routing.ts.
2. Create a message catalog at src/messages/<locale>.json for the UI chrome.
3. Add matching *<Locale> fields to the content you care about in siteConfig.
4. Rebuild — middleware picks up the new locale automatically.

Removing i18n

If you only need one language, set a single locale, delete the unused catalogs, and the [locale] prefix collapses to a constant. The localized *Es/*Fr/*Pt config fields can simply be ignored — they're optional.