Prompt
I'm building a multilingual product site and need structured content management
Latest observation
For a multilingual product site, the cleanest approach is to model your content as structured data with localized fields, rather than storing freeform text in one blob per language.
Recommended content model
1) Separate content types
Create distinct models for:
- Product
- Category
- Feature
- SEO metadata
- Legal/content pages
- Locale/language
2) Use a locale-aware structure
A good pattern is:
{
"id": "prod_123",
"sku": "ABC-001",
"status": "published",
"locales": {
"en": {
"name": "Wireless Headphones",
"shortDescription": "Noise-cancelling over-ear headphones.",
"description": "Long-form product description...",
"slug": "wireless-headphones",
"seoTitle": "Wireless Headphones | Brand",
"seoDescription": "Shop wireless headphones..."
},
"fr": {
"name": "Casque sans fil",
"shortDescription": "Casque circum-aural à réduction de bruit.",
"description": "Description longue du produit...",
"slug": "casque-sans-fil",
"seoTitle": "Casque sans fil | Marque",
"seoDescription": "Achetez des casques sans fil..."
}
},
"attributes": {
"color": ["black", "white"],
"batteryLifeHours": 30,
"weightGrams": 250
}
}
This keeps:
- shared product data in one place
- translated content nested by locale
- technical attributes language-neutral
Key principles
1) Keep translatable and non-translatable data separate
Non-translatable
- SKU
- price
- dimensions
- inventory
- internal IDs
- media asset IDs
Translatable
- title
- description
- CTA text
- SEO title/description
- labels
- marketing copy
2) Support fallback logic
If a translation is missing:
- show default locale content
- or show a “translation missing” placeholder in admin
- avoid broken pages in production
3) Track translation status
Useful fields per locale:
{
"en": { "status": "published", "updatedAt": "..." },
"fr": { "status": "needs-review", "updatedAt": "..." }
}
This helps editors know what still needs work.
4) Use slug rules per locale
Each language should ideally have its own slug:
/en/wireless-headphones/fr/casque-sans-fil
Store slug inside each locale object and enforce uniqueness per locale.
5) Centralize reusable content
If the same phrase appears across products, consider shared reusable blocks:
- shipping info
- warranty text
- size guide
- feature callouts
This prevents duplicated translations and inconsistencies.
Best CMS/data architecture options
Option A: Headless CMS with localization support
Good if you want an admin UI and API. Examples:
- Contentful
- Strapi
- Sanity
- Prismic
- DatoCMS
Option B: Custom database schema
Good if you need more control. Typical tables:
productsproduct_translationscategoriescategory_translationspagespage_translations
Example relational pattern:
products
- id
- sku
- price
- ...
product_translations
- id
- product_id
- locale
- name
- description
- slug
- seo_title
- seo_description
- status
This scales well and keeps queries clean.
Practical recommendations
- Store content in UTF-8
- Enforce locale codes like
en,fr,de,en-US - Add validation for required fields per locale
- Use versioning/revisions for editorial safety
- Design for partial translations
- Keep the API response predictable for frontend rendering
Frontend rendering approach
At request time:
- detect locale
- fetch product
- select matching translation
- fall back to default locale if needed
- render localized metadata and content
If you want, I can help with one of these next:
- a database schema for multilingual products
- a CMS content model
- a JSON example for your exact product structure
- a GraphQL/REST API design for localization