@intlayer/docs 7.3.3 → 7.3.5

package/docs/en/per_locale_file.md

@@ -15,6 +15,9 @@ slugs:
   - 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
@@ -33,83 +36,6 @@ This flexibility enables:
 - Support for automated translation workflows
 - Clear organization of translations into separate, locale-specific files
 
-## 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"
-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.mjs" contentDeclarationFormat="esm"
-import { t } from "intlayer";
-
-/** @type {import('intlayer').Dictionary} */
-const helloWorldContent = {
-  key: "hello-world",
-  content: {
-    multilingualContent: t({
-      en: "Title of my component",
-      es: "Título de mi componente",
-    }),
-  },
-};
-
-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.
-
 ## Per-Locale Format
 
 This format is useful when:
@@ -225,6 +151,101 @@ module.exports = helloWorldContent;
 
 > 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 `transform` command, and the compiler. (See [Compiler](https://intlayer.org/doc/compiler) or [Transform](https://intlayer.org/doc/concept/cli/transform) for more information.)
+
+## 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"
+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.mjs" contentDeclarationFormat="esm"
+import { t } from "intlayer";
+
+/** @type {import('intlayer').Dictionary} */
+const helloWorldContent = {
+  key: "hello-world",
+  content: {
+    multilingualContent: t({
+      en: "Title of my component",
+      es: "Título de mi componente",
+    }),
+  },
+};
+
+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:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intlayer/docs",
-  "version": "7.3.3",
+  "version": "7.3.5",
   "private": false,
   "description": "Intlayer documentation",
   "keywords": [
@@ -73,13 +73,13 @@
     "watch": "webpack --config ./webpack.config.ts --watch"
   },
   "dependencies": {
-    "@intlayer/config": "7.3.3",
-    "@intlayer/core": "7.3.3",
-    "@intlayer/types": "7.3.3"
+    "@intlayer/config": "7.3.5",
+    "@intlayer/core": "7.3.5",
+    "@intlayer/types": "7.3.5"
   },
   "devDependencies": {
-    "@intlayer/api": "7.3.3",
-    "@intlayer/cli": "7.3.3",
+    "@intlayer/api": "7.3.5",
+    "@intlayer/cli": "7.3.5",
     "@types/node": "24.10.1",
     "@utils/ts-config": "1.0.4",
     "@utils/ts-config-types": "1.0.4",