better-i18n.com
Developer DocsHelp CenterChangelog

What is the Content CMS?

Updated Aug 21, 2026

The Content CMS in Better i18n lets you manage structured multilingual content — articles, blog posts, help docs, product descriptions — in the same platform as your i18n keys.

Translation keys vs. content entries #

Better i18n manages two types of content:

TypeWhat it isExample
Translation keysShort strings used in your codeauth.login_button = "Sign in"
Content entriesStructured documents with rich bodiesA full help article or blog post

Most apps use both. Translation keys for UI strings; content entries for longer-form content.

What the Content CMS gives you #

  • Content models — define the schema for your content types (custom fields, field types, localized fields)
  • Entries — create and manage individual pieces of content
  • Multilingual — every entry can have translations in all your project's languages
  • Read API + edge cache — content is served from https://content.better-i18n.com, cached at the edge and purged when you publish
  • MCP tools — AI agents can create, translate, and publish content directly
  • Version history — models can keep a revision per save, so you can look back at what a language said before

How content reaches your app #

Code
Dashboard / MCP agent
  → Create/edit entry with translations
  → Publish
  → Content API cache purged, new version served
  → Your app fetches at runtime

No rebuild needed. Content updates are live as soon as you publish.

Note which surfaces do what: the dashboard and MCP write content; the Content API only reads it. Your app holds a key that can fetch content and nothing else.

Content API endpoint #

Code
https://content.better-i18n.com/v1/content/{org}/{project}/models/{model}/entries

Example:

Bash
curl "https://content.better-i18n.com/v1/content/acme/docs/models/help-article/entries?language=en&status=published" \
  -H "x-api-key: YOUR_API_KEY"

Two details that save a support ticket: authentication is the x-api-key header (not Authorization: Bearer), and the API does not filter by status on its own — without status=published you get drafts back too.

Who is this for? #

The Content CMS is useful for:

  • Documentation sites — help centers, knowledge bases
  • Marketing content — landing pages, blog posts
  • Product content — feature descriptions, changelogs
  • Dynamic content — anything you want to update without redeploying

Next steps #