aymericzip/intlayer-skills / skills/intlayer-content
intlayer-content
VerifiedDefine rich content structures using Intlayer content nodes. Use when the user asks to "create translations", "handle pluralization", "use markdown in content", or implement "conditional content".
| File | Kind | Size |
|---|---|---|
| LICENCE.md | markdown | 10.7 KB |
| SKILL.md | skill md | 12.0 KB |
| references/concept_content.md | markdown | 35.4 KB |
| references/concept_content_condition.md | markdown | 7.7 KB |
| references/concept_content_enumeration.md | markdown | 13.6 KB |
| references/concept_content_file.md | markdown | 8.4 KB |
| references/concept_content_function-fetching.md | markdown | 4.6 KB |
| references/concept_content_gender.md | markdown | 7.9 KB |
| references/concept_content_html.md | markdown | 22.7 KB |
| references/concept_content_insertion.md | markdown | 4.7 KB |
| references/concept_content_markdown.md | markdown | 47.2 KB |
| references/concept_content_nesting.md | markdown | 8.7 KB |
| references/concept_content_plural.md | markdown | 11.3 KB |
| references/concept_content_select.md | markdown | 10.6 KB |
| references/concept_content_translation.md | markdown | 6.1 KB |
| references/concept_per-locale-file.md | markdown | 7.6 KB |
| references/packages_intlayer_exports.md | markdown | 12.4 KB |
references/concept_per-locale-file.md
View on GitHub---
createdAt: 2025-04-18
updatedAt: 2026-09-27
priority: 8
title: "Per-Locale Content Declaration Files"
description: Discover how to declare content per locale in Intlayer. Follow the documentation to understand the different formats and use cases.
keywords:
- Internationalization
- Documentation
- Intlayer
- Per-Locale
- TypeScript
- JavaScript
slugs:
- doc
- concept
- per-locale-file
history:
- version: 7.3.1
date: 2025-11-29
changes: "Add global configuration for per-locale files"
- version: 5.5.10
date: 2025-06-29
changes: "Init history"
author: aymericzip
---
# Declaration of `Per-Locale` Content Declaration in Intlayer
Intlayer supports two ways to declare multilingual content:
- Single file with all translations
- One file per locale (per-locale format)
This flexibility enables:
- Easy migration from other i18n tools
- Support for automated translation workflows
- Clear organization of translations into separate, locale-specific files
## Per-Locale Format
This format is useful when:
- You want to version or override translations independently.
- You're integrating machine or human translation workflows.
You can also split translations into individual locale files by specifying the locale field:
```tsx fileName="hello-world.en.content.ts" contentDeclarationFormat=["typescript", "esm", "cjs"]
import { t, Locales, type Dictionary } from "intlayer";
const helloWorldContent = {
key: "hello-world",
locale: Locales.ENGLISH, // Important
content: { multilingualContent: "Title of my component" },
} satisfies Dictionary;
export default helloWorldContent;
```
```tsx fileName="hello-world.es.content.ts" contentDeclarationFormat={["typescript", "esm"]}
import { t, Locales, type Dictionary } from "intlayer";
const helloWorldContent = {
key: "hello-world",
locale: Locales.SPANISH, // Important
content: { multilingualContent: "Título de mi componente" },
} satisfies Dictionary;
export default helloWorldContent;
```
```json5 fileName="hello-world.en.content.json" contentDeclarationFormat="json"
{
"$schema": "https://intlayer.org/schema.json",
"key": "hello-world",
"locale": "en", // Important
"content": {
"multilingualContent": "Title of my component",
},
}
```
```json5 fileName="hello-world.es.content.json" contentDeclarationFormat="json"
{
"$schema": "https://intlayer.org/schema.json",
"key": "hello-world",
"locale": "es", // Important
"content": {
"multilingualContent": "Título de mi componente",
},
}
```
> Important: Make sure the locale field is defined. It tells Intlayer which language the file represents.
> Note: In both cases, the content declaration file must follow the naming pattern `*.content.{ts,tsx,js,jsx,mjs,cjs,json}` to be recognized by Intlayer. The `.[locale]` suffix is optional and used only as a naming convention.
### Global Configuration for Per-Locale Files
You can configure the global configuration for per-locale files by adding the following to your `intlayer.config.ts` file:
```ts
import { Locales, type IntlayerConfig } from "intlayer";
const config: IntlayerConfig = {
dictionary: {
locale: Locales.ENGLISH,
},
};
export default config;
```
Using this configuration, all per-locale files will be generated with the default locale set to English. It also include generation of `.content` files using the `extract` command, and the compiler. (See [Compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md) or [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) for more information.)
- [Compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md)
## Single File with Multiple Translations
This format is ideal for:
- Quick iteration in code.
- Seamless integration with the CMS.
This is the recommended approach for most use cases. It centralizes translations, making it easy to iterate and integrate with the CMS.
```tsx fileName="hello-world.content.ts" contentDeclarationFormat={["typescript", "esm"]}
import { t, type Dictionary } from "intlayer";
const helloWorldContent = {
key: "hello-world",
content: {
multilingualContent: t({
en: "Title of my component",
es: "Título de mi componente",
}),
},
} satisfies Dictionary;
export default helloWorldContent;
```
```js fileName="hello-world.content.cjs" contentDeclarationFormat="json"
const { t } = require("intlayer");
/** @type {import('intlayer').Dictionary} */
const helloWorldContent = {
key: "hello-world",
content: {
multilingualContent: t({
en: "Title of my component",
es: "Título de mi componente",
}),
},
};
module.exports = helloWorldContent;
```
```json fileName="hello-world.content.ts" contentDeclarationFormat="json"
{
"$schema": "https://intlayer.org/schema.json",
"key": "hello-world",
"content": {
"multilingualContent": {
"nodeType": "translation",
"translation": {
"en": "Title of my component",
"es": "Título de mi componente"
}
}
}
}
```
> Recommended: This format is best when using Intlayer's visual editor or managing translations directly in the code.
## Mixing Formats
You can combine both declaration approaches for the same content key. For example:
- Declare your base content statically in a file like index.content.ts.
- Add or override specific translations in separate files such as index.fr.content.ts or index.content.json.
This setup is especially useful when:
- You want to define the initial content structure in code.
- You plan to enrich or complete translations later using the CMS or automated tools.
```bash codeFormat="typescript"
.
└── Components
└── MyComponent
├── index.content.ts
├── index.content.json
└── index.ts
```
### Example
Here a multilingual content declaration file:
```tsx fileName="Components/MyComponent/index.content.ts"
import { t, type Dictionary } from "intlayer";
const helloWorldContent = {
key: "hello-world",
locale: Locales.ENGLISH,
content: {
multilingualContent: "Title of my component",
projectName: "My project",
},
} satisfies Dictionary;
export default helloWorldContent;
```
```json fileName="Components/MyComponent/index.content.json"
{
"$schema": "https://intlayer.org/schema.json",
"key": "hello-world",
"content": {
"multilingualContent": {
"nodeType": "translation",
"translation": {
"fr": "Titre de mon composant",
"es": "Título de mi componente"
}
}
}
}
```
Intlayer merges multilingual and per-locale files automatically.
```tsx fileName="Components/MyComponent/index.ts"
import { getIntlayer, Locales } from "intlayer";
const intlayer = getIntlayer("hello-world"); // Default locale is ENGLISH, so it will return the ENGLISH content
console.log(JSON.stringify(intlayer, null, 2));
// Result:
// {
// "multilingualContent": "Title of my component",
// "projectName": "My project"
// }
const intlayer = getIntlayer("hello-world", Locales.SPANISH);
console.log(JSON.stringify(intlayer, null, 2));
// Result:
// {
// "multilingualContent": "Título de mi componente",
// "projectName": "My project"
// }
const intlayer = getIntlayer("hello-world", Locales.FRENCH);
console.log(JSON.stringify(intlayer, null, 2));
// Result:
// {
// "multilingualContent": "Titre de mon composant",
// "projectName": "My project"
// }
```
### Automatic Translation Generation
Use the [intlayer CLI](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md) to auto-fill missing translations based on your preferred services.
- [intlayer CLI](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |