Localise content

5 min read

Localisation is built in, not bolted on. Every entry can carry a version per locale, sharing the same content type and fields, so translators work against a familiar structure rather than a fresh layout per language.

Add locales

Your project starts with en-gb as the default. Add the locales your audience needs in project settings — Starter includes two, Pro includes ten, Enterprise lifts the limit. Each entry then offers a version for each locale.

Request a language

Pass ?lang= to any delivery request to get that locale. Ask for fr-fr and you get French; omit it and you get the project default.

curl

curl "https://your-domain.com/api/v1/your-project/documents?lang=fr-fr" \
  -H "Authorization: Bearer mjmt_your_public_read_token"

When a translation has not been written yet, Mojimoto falls back to your default locale so pages never render empty.

Model your content

Design content types with typed fields, reusable components, and references — a model your front end can rely on.

Fetch content with the Delivery API

Query published content by type, slug and locale, paginate, sort, and resolve references — all from one REST endpoint.

Add locales

Request a language

Build it for real