Caratteristica

Multilingual Headless CMS — Manage Localized Content at Scale

Why Your CMS Needs Native i18n Support

Most headless CMS platforms treat localization as an afterthought — a plugin, an add-on, or a field-level toggle buried in settings. The result? Fragmented workflows, inconsistent translations, and engineering teams building custom glue code to hold it all together.

Better i18n's Headless CMS is different. Multilingual content management is the foundation, not a feature flag. Every model, every field, every API response is designed to work across languages from day one.

Model Builder — Structure Content Your Way

The Model Builder lets you define exactly how your content is structured. Create collections for repeated content (blog posts, product pages, FAQs) or singletons for one-off pages (homepage, about, settings).

Each model is a schema that your team and your API consumers can rely on. No more guessing what fields exist or what format they expect — the model is the contract.

19+ Field Types

Better i18n ships with a comprehensive set of field types so you can model any content structure without workarounds:

  • Text & Rich Text — Plain text fields and a full Plate.js rich text editor with formatting, embeds, and structured content
  • Textarea — Multi-line plain text for descriptions, summaries, and notes
  • Number & Boolean — Numeric values and true/false toggles
  • Date & DateTime — Date pickers with optional time precision
  • Files & Media — Upload and attach images, documents, and other assets
  • URL, Email & Phone — Validated fields for contact and link data
  • Enum (Select / Multi-select) — Predefined option lists for consistent categorization
  • Relations & Rollups — Link entries across models and aggregate related data
  • Formulas — Computed fields based on other field values
  • Unique ID — Auto-generated identifiers for each entry
  • Status — Built-in workflow states for content lifecycle management
  • Created / Last Edited Timestamps — Automatic audit trail for every entry

Field Management

Every field can be configured with precision:

  • Add new fields to any model at any time
  • Edit field names, types, validation rules, and placeholder text
  • Reorder fields via drag-and-drop to match your editorial workflow
  • Delete fields you no longer need — safely and without breaking existing entries

Entry Management — Full Content Lifecycle

Creating and managing content entries is straightforward. The entry editor adapts to your model's schema, presenting the right input for each field type.

CRUD + Bulk Operations

  • Create entries with all custom fields populated
  • Read entries with full field expansion and relation resolution
  • Update any field, including translations for each language
  • Delete entries individually or in bulk
  • Bulk status updates — move dozens of entries from draft to published in one action
  • Bulk delete — clean up outdated content efficiently

Status Workflow

Every entry follows a clear lifecycle:

  1. Draft — Work in progress, visible only to editors
  2. Pending Review — Ready for editorial review
  3. Published — Live and available via the API
  4. Archived — Retained for reference but removed from active queries

This workflow ensures content quality without slowing down your team.

AI Content Generation

Staring at a blank field? Better i18n's AI content generation can help. The content.generateFieldContent capability analyzes your model structure and existing content to suggest field values — from SEO meta descriptions to product copy.

AI generation works at the field level, so you stay in control. Accept, edit, or regenerate until the content matches your voice.

Public REST API — Deliver Content Anywhere

The headless architecture means your content is available wherever you need it — websites, mobile apps, digital signage, IoT devices, or any frontend framework.

API Endpoints

EndpointDescription
GET /v1/content/:orgSlug/:projectSlug/modelsList all content models
GET /v1/content/:orgSlug/:projectSlug/entriesList entries with filtering
GET /v1/content/:orgSlug/:projectSlug/entries/:entrySlugGet a single entry by slug

Query Parameters

The API supports rich querying out of the box:

  • language — Return content in a specific language
  • status — Filter by draft, published, or archived
  • page & limit — Paginate large result sets
  • sort & order — Sort by any field, ascending or descending
  • fields — Select only the fields you need (sparse fieldsets)
  • expand — Resolve relation fields inline (no N+1 queries)
  • search — Full-text search across entry titles and text fields
  • filter[fieldName] — Filter by any custom field value

Authentication

Secure your content with API key authentication. Create and manage keys through the dashboard, then pass them via the x-api-key header.

GET /v1/content/acme/website/entries?language=de&status=published
x-api-key: your-api-key

Localized Content Management Done Right

What makes this headless CMS different from the dozens of others on the market? Every feature is designed with multilingual content in mind:

  • Per-field localization — Mark which fields need translation and which are universal (like dates or booleans)
  • Language-aware API — Request content in any language with a single query parameter
  • Translation status tracking — See which entries are missing translations at a glance
  • Consistent slugs — Entries maintain the same slug across languages for clean URL structures

Get Started

Better i18n's Headless CMS is available as part of the Better i18n platform. Define your first model, create entries in your source language, and start delivering localized content through the API in minutes — not weeks.

Start building your multilingual CMS →