@intlayer/docs 6.1.6 → 7.0.0-canary.1

package/docs/en/autoFill.md

@@ -15,13 +15,68 @@ slugs:
   - doc
   - concept
   - auto-fill
+history:
+  - version: 7.0.0
+    date: 2025-10-23
+    changes: Rename `autoFill` to `fill` and update behavior
+  - version: 6.0.0
+    date: 2025-09-20
+    changes: Add global configuration
+  - version: 6.0.0
+    date: 2025-09-17
+    changes: Add `{{fileName}}` variable
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
-# Autofill Content Declaration File Translations
+# Fill Content Declaration File Translations
 
-**Autofill content declaration files** are a way to speed up your development workflow.
+**Autofill content declaration files** in your CI are a way to speed up your development workflow.
 
-The autofill mechanism works through a _master-slave_ relationship between content declaration files. When the main (master) file is updated, Intlayer will automatically apply those changes to the derived (autofilled) declaration files.
+## Default Behavior
+
+By default, `fill` is set to `true` globally, which means Intlayer will automatically fill all content files and edit the file itself. This behavior can be customized in several ways:
+
+### Global Configuration Options
+
+1. **`fill: true` (default)** - Automatically fill all locales and edit the current file
+2. **`fill: false`** - Disable auto-fill for this content file
+3. **`fill: "path/to/file"`** - Create/update the specified file without editing the current one
+4. **`fill: { [key in Locales]?: string }`** - Create/update the specified file for each locale
+
+### v7 Behavior Changes
+
+In v7, the `fill` command behavior has been updated:
+
+- **`fill: true`** - Rewrites the current file with filled content for all locales
+- **`fill: "path/to/file"`** - Fills the specified file without modifying the current file
+- **`fill: false`** - Disables auto-fill completely
+
+When using a path option to write to another file, the fill mechanism works through a _master-slave_ relationship between content declaration files. The main (master) file serves as the source of truth, and when it's updated, Intlayer will automatically apply those changes to the derived (filled) declaration files specified by the path.
+
+### Per-Locale Customization
+
+You can also customize the behavior for each locale by using an object:
+
+```ts fileName="intlayer.config.ts"
+const config: IntlayerConfig = {
+  content: {
+    internationalization: {
+      locales: [Locales.ENGLISH, Locales.FRENCH, Locales.POLISH],
+      defaultLocale: Locales.ENGLISH,
+      requiredLocales: [Locales.ENGLISH], // Recommended to avoid Property 'pl' is missing in type '{ en: string; xxx } on your t function if
+    },
+    fill: {
+      en: true, // Fill and edit the current file for English
+      fr: "./translations/fr.json", // Create separate file for French
+      es: false, // Disable fill for Spanish
+    },
+  },
+};
+```
+
+This allows you to have different fill behaviors for different locales within the same project.
 
 ```ts fileName="src/components/example/example.content.ts"
 import { Locales, type Dictionary } from "intlayer";
@@ -29,7 +84,7 @@ import { Locales, type Dictionary } from "intlayer";
 const exampleContent = {
   key: "example",
   locale: Locales.ENGLISH,
-  autoFill: "./example.content.json",
+  fill: "./example.content.json",
   content: {
     contentExample: "This is an example of content",
   },
@@ -38,7 +93,7 @@ const exampleContent = {
 export default exampleContent;
 ```
 
-Here is a [per-locale content declaration file](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/per_locale_file.md) using the `autoFill` instruction.
+Here is a [per-locale content declaration file](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/per_locale_file.md) using the `fill` instruction.
 
 Then, when you run the following command:
 
@@ -80,13 +135,13 @@ const config: IntlayerConfig = {
   },
   content: {
     // Auto-generate missing translations for all dictionaries
-    autoFill: "./{{fileName}}Filled.content.ts",
+    fill: "./{{fileName}}Filled.content.ts",
     //
-    // autoFill: "/messages/{{locale}}/{{key}}/{{fileName}}.content.json",
+    // fill: "/messages/{{locale}}/{{key}}/{{fileName}}.content.json",
     //
-    // autoFill: true, // auto-generate missing translations for all dictionaries like using "./{{fileName}}.content.json"
+    // fill: true, // auto-generate missing translations for all dictionaries like using "./{{fileName}}.content.json"
     //
-    // autoFill: {
+    // fill: {
     //   en: "./{{fileName}}.en.content.json",
     //   fr: "./{{fileName}}.fr.content.json",
     //   es: "./{{fileName}}.es.content.json",
@@ -97,7 +152,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-You can still fine‑tune per dictionary using the `autoFill` field in content files. Intlayer will first consider the per dictionary configuration and then fallback to the global configuration.
+You can still fine‑tune per dictionary using the `fill` field in content files. Intlayer will first consider the per dictionary configuration and then fallback to the global configuration.
 
 ## Autofilled File Format
 
@@ -106,7 +161,7 @@ The recommended format for autofilled declaration files is **JSON**, which helps
 ```ts fileName="src/components/example/example.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: "./example.filled.content.ts",
+  fill: "./example.filled.content.ts",
   content: {
     // Your content
   },
@@ -126,12 +181,12 @@ src/components/example/example.filled.content.ts
 
 ## Absolute Paths
 
-The `autoFill` field also supports absolute paths.
+The `fill` field also supports absolute paths.
 
 ```ts fileName="src/components/example/example.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: "/messages/example.content.json",
+  fill: "/messages/example.content.json",
   content: {
     // Your content
   },
@@ -146,12 +201,12 @@ This will generate the file at:
 
 ## Autogenerate Per-Locale Content Declaration Files
 
-The `autoFill` field also supports generation of **per-locale** content declaration files.
+The `fill` field also supports generation of **per-locale** content declaration files.
 
 ```ts fileName="src/components/example/example.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: {
+  fill: {
     fr: "./example.fr.content.json",
     es: "./example.es.content.json",
   },
@@ -170,12 +225,12 @@ This will generate two separate files:
 
 ## Filter Specific Locale Autofill
 
-Using an object for the `autoFill` field allows you to apply filters and generate only specific locale files.
+Using an object for the `fill` field allows you to apply filters and generate only specific locale files.
 
 ```ts fileName="src/components/example/example.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: {
+  fill: {
     fr: "./example.fr.content.json",
   },
   content: {
@@ -188,7 +243,7 @@ This will only generate the French translation file.
 
 ## Path Variables
 
-You can use variables inside the `autoFill` path to dynamically resolve the target paths for the generated files.
+You can use variables inside the `fill` path to dynamically resolve the target paths for the generated files.
 
 **Available variables:**
 
@@ -199,7 +254,7 @@ You can use variables inside the `autoFill` path to dynamically resolve the targ
 ```ts fileName="src/components/example/index.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: "/messages/{{locale}}/{{key}}.content.json",
+  fill: "/messages/{{locale}}/{{key}}.content.json",
   content: {
     // Your content
   },
@@ -214,7 +269,7 @@ This will generate:
 ```ts fileName="src/components/example/index.content.ts"
 const exampleContent = {
   key: "example",
-  autoFill: "./{{fileName}}.content.json",
+  fill: "./{{fileName}}.content.json",
   content: {
     // Your content
   },
@@ -225,11 +280,3 @@ This will generate:
 
 - `./index.content.json`
 - `./index.content.json`
-
-## Doc History
-
-| Version | Date       | Changes                     |
-| ------- | ---------- | --------------------------- |
-| 6.0.0   | 2025-09-20 | Add global configuration    |
-| 6.0.0   | 2025-09-17 | Add `{{fileName}}` variable |
-| 5.5.10  | 2025-06-29 | Init history                |

package/docs/en/configuration.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-13
-updatedAt: 2025-09-26
+updatedAt: 2025-10-21
 title: Configuration
 description: Learn how to configure Intlayer for your application. Understand the various settings and options available to customize Intlayer to your needs.
 keywords:
@@ -13,6 +13,37 @@ slugs:
   - doc
   - concept
   - configuration
+history:
+  - version: 7.0.0
+    date: 2025-10-21
+    changes: Replace `middleware` by `routing` configuration
+  - version: 7.0.0
+    date: 2025-10-12
+    changes: Add `formatCommand` option
+  - version: 6.2.0
+    date: 2025-10-12
+    changes: Update `excludedPath` option
+  - version: 6.0.2
+    date: 2025-09-23
+    changes: Add `outputFormat` option
+  - version: 6.0.0
+    date: 2025-09-21
+    changes: Remove `dictionaryOutput` field and `i18nextResourcesDir` field
+  - version: 6.0.0
+    date: 2025-09-16
+    changes: Add `live` import mode
+  - version: 6.0.0
+    date: 2025-09-04
+    changes: Replace `hotReload` field by `liveSync` and add `liveSyncPort` and `liveSyncURL` fields
+  - version: 5.6.1
+    date: 2025-07-25
+    changes: Replace `activateDynamicImport` with `importMode` option
+  - version: 5.6.0
+    date: 2025-07-13
+    changes: Change default contentDir from `['src']` to `['.']`
+  - version: 5.5.11
+    date: 2025-06-29
+    changes: Add `docs` commands
 ---
 
 # Intlayer Configuration Documentation
@@ -256,12 +287,72 @@ Defines settings related to the integrated editor, including server port and act
   - _Example_: `'https://example.com'`
   - _Note_: Point to localhost by default but can be changed to any URL in the case of a remote live sync server.
 
-### Middleware Configuration
+- **formatCommand**:
+  - _Type_: `string`
+  - _Default_: `undefined`
+  - _Description_: The command to format the content. When intlayer write your .content files locally, this command will be used to format the content.
+  - _Example_: `'npx prettier --write "{{file}}" --log-level silent'` Using Prettier
+  - _Example_: `'npx biome format "{{file}}" --write --log-level none'` Using Biome
+  - _Example_: `'npx eslint --fix "{{file}}"  --quiet'` Using ESLint
+  - _Note_: Intlayer will replace the {{file}} with the path of the file to format.
 
-Settings that control middleware behavior, including how the application handles cookies, headers, and URL prefixes for locale management.
+### Routing Configuration
+
+Settings that control routing behavior, including URL structure, locale storage, and middleware handling.
 
 #### Properties
 
+- **mode**:
+  - _Type_: `'prefix-no-default' | 'prefix-all' | 'no-prefix' | 'search-params'`
+  - _Default_: `'prefix-no-default'`
+  - _Description_: URL routing mode for locale handling.
+  - _Examples_:
+    - `'prefix-no-default'`: `/dashboard` (en) or `/fr/dashboard` (fr)
+    - `'prefix-all'`: `/en/dashboard` (en) or `/fr/dashboard` (fr)
+    - `'no-prefix'`: `/dashboard` (locale handled via other means)
+    - `'search-params'`: `/dashboard?locale=fr`
+  - _Note_: This setting does not impact cookie or locale storage management.
+
+- **storage**:
+  - _Type_: `false | 'cookie' | 'localStorage' | 'sessionStorage' | CookiesAttributes | LocaleStorageAttributes | Array`
+  - _Default_: `'localStorage'`
+  - _Description_: Configuration for storing the locale in the client.
+  - _Examples_:
+
+    ```typescript
+    // Disable storage
+    storage: false
+
+    // Simple storage types
+    storage: 'cookie'
+    storage: 'localStorage'
+    storage: 'sessionStorage'
+
+    // Cookie with custom attributes
+    storage: {
+      type: 'cookie',
+      name: 'custom-locale',
+      domain: '.example.com',
+      secure: true,
+      sameSite: 'strict'
+    }
+
+    // localStorage with custom key
+    storage: {
+      type: 'localStorage',
+      name: 'custom-locale'
+    }
+
+    // Multiple storage types
+    storage: ['cookie', 'localStorage']
+    ```
+
+  - _Note_:
+    - If `false`, the locale will not be stored by the middleware
+    - Check GDPR compliance for cookies. See https://gdpr.eu/cookies/
+    - Recommendation: Configure both localStorage and cookies for GDPR compliance
+    - Disable cookie storage by default on the useLocale hook until user consent
+
 - **headerName**:
   - _Type_: `string`
   - _Default_: `'x-intlayer-locale'`
@@ -269,22 +360,6 @@ Settings that control middleware behavior, including how the application handles
   - _Example_: `'x-custom-locale'`
   - _Note_: This is useful for API-based locale determination.
 
-- **cookieName**:
-  - _Type_: `string`
-  - _Default_: `'intlayer-locale'`
-  - _Description_: The name of the cookie used to store the locale.
-  - _Example_: `'custom-locale'`
-  - _Note_: Used to persist the locale across sessions.
-
-- **prefixDefault**:
-  - _Type_: `boolean`
-  - _Default_: `false`
-  - _Description_: Whether to include the default locale in the URL.
-  - _Example_: `true`
-  - _Note_:
-    - If `true` and `defaultLocale = 'en'`: path = `/en/dashboard` or `/fr/dashboard`
-    - If `false` and `defaultLocale = 'en'`: path = `/dashboard` or `/fr/dashboard`
-
 - **basePath**:
   - _Type_: `string`
   - _Default_: `''`
@@ -296,26 +371,6 @@ Settings that control middleware behavior, including how the application handles
     - The URL will be `https://example.com/my-app/en`
     - If the base path is not set, the URL will be `https://example.com/en`
 
-- **serverSetCookie**:
-  - _Type_: `string`
-  - _Default_: `'always'`
-  - _Description_: Rule for setting the locale cookie on the server.
-  - _Options_: `'always'`, `'never'`
-  - _Example_: `'never'`
-  - _Note_: Controls whether the locale cookie is set on every request or never.
-
-- **noPrefix**:
-  - _Type_: `boolean`
-  - _Default_: `false`
-  - _Description_: Whether to omit the locale prefix from URLs.
-  - _Example_: `true`
-  - _Note_:
-    - If `true`: No prefix in the URL
-    - If `false`: Prefix in the URL
-    - Example with `basePath = '/my-app'`:
-      - If `noPrefix = false`: URL will be `https://example.com/my-app/en`
-      - If `noPrefix = true`: URL will be `https://example.com`
-
 - **detectLocaleOnPrefetchNoPrefix**:
   - _Type_: `boolean`
   - _Default_: `false`
@@ -340,6 +395,120 @@ Settings that control middleware behavior, including how the application handles
       - You want to optimize prefetching performance
       - You want to avoid potential redirect loops
 
+#### Cookie Attributes
+
+When using cookie storage, you can configure additional cookie attributes:
+
+- **name**: Cookie name (default: `'INTLAYER_LOCALE'`)
+- **domain**: Cookie domain (default: undefined)
+- **path**: Cookie path (default: undefined)
+- **secure**: Require HTTPS (default: undefined)
+- **httpOnly**: HTTP-only flag (default: undefined)
+- **sameSite**: SameSite policy (`'strict' | 'lax' | 'none'`)
+- **expires**: Expiration date or days (default: undefined)
+
+#### Locale Storage Attributes
+
+When using localStorage or sessionStorage:
+
+- **type**: Storage type (`'localStorage' | 'sessionStorage'`)
+- **name**: Storage key name (default: `'INTLAYER_LOCALE'`)
+
+#### Configuration Examples
+
+Here are some common configuration examples for the new v7 routing structure:
+
+**Basic Configuration (Default)**:
+
+```typescript
+// intlayer.config.ts
+export default defineConfig({
+  internationalization: {
+    locales: ["en", "fr", "es"],
+    defaultLocale: "en",
+  },
+  routing: {
+    mode: "prefix-no-default",
+    storage: "localStorage",
+    headerName: "x-intlayer-locale",
+    basePath: "",
+    detectLocaleOnPrefetchNoPrefix: false,
+  },
+});
+```
+
+**GDPR Compliant Configuration**:
+
+```typescript
+// intlayer.config.ts
+export default defineConfig({
+  internationalization: {
+    locales: ["en", "fr", "es"],
+    defaultLocale: "en",
+  },
+  routing: {
+    mode: "prefix-no-default",
+    storage: [
+      {
+        type: "localStorage",
+        name: "user-locale",
+      },
+      {
+        type: "cookie",
+        name: "user-locale",
+        secure: true,
+        sameSite: "strict",
+        httpOnly: false,
+      },
+    ],
+    headerName: "x-intlayer-locale",
+    basePath: "",
+    detectLocaleOnPrefetchNoPrefix: false,
+  },
+});
+```
+
+**Search Parameters Mode**:
+
+```typescript
+// intlayer.config.ts
+export default defineConfig({
+  internationalization: {
+    locales: ["en", "fr", "es"],
+    defaultLocale: "en",
+  },
+  routing: {
+    mode: "search-params",
+    storage: "localStorage",
+    headerName: "x-intlayer-locale",
+    basePath: "",
+    detectLocaleOnPrefetchNoPrefix: false,
+  },
+});
+```
+
+**No Prefix Mode with Custom Storage**:
+
+```typescript
+// intlayer.config.ts
+export default defineConfig({
+  internationalization: {
+    locales: ["en", "fr", "es"],
+    defaultLocale: "en",
+  },
+  routing: {
+    mode: "no-prefix",
+    storage: {
+      type: "sessionStorage",
+      name: "app-locale",
+    },
+    headerName: "x-custom-locale",
+    basePath: "/my-app",
+    detectLocaleOnPrefetchNoPrefix: true,
+  },
+});
+```
+
 ---
 
 ### Content Configuration
@@ -348,7 +517,7 @@ Settings related to content handling within the application, including directory
 
 #### Properties
 
-- **autoFill**:
+- **fill**:
   - _Type_: `boolean | string | { [key in Locales]?: string }`
   - _Default_: `undefined`
   - _Description_: Indicate how the content should be automatically filled using AI. Can be declared globally in the `intlayer.config.ts` file.
@@ -356,9 +525,10 @@ Settings related to content handling within the application, including directory
   - _Example_: `'./{{fileName}}.content.json'`
   - _Example_: `{ fr: './{{fileName}}.fr.content.json', es: './{{fileName}}.es.content.json' }`
   - _Note_: The auto fill configuration. It can be:
-    - boolean: Enable auto fill for all locales
-    - string: Path to a single file or template with variables
-    - object: Per-locale file paths
+    - `true`: Rewrites the current file with filled content for all locales
+    - `false`: Disables auto-fill completely
+    - `string`: Path to a single file or template with variables (fills the specified file without modifying the current one)
+    - `object`: Per-locale file paths
 
 - **watch**:
   - _Type_: `boolean`
@@ -423,7 +593,7 @@ Settings related to content handling within the application, including directory
 
 - **excludedPath**:
   - _Type_: `string[]`
-  - _Default_: `['node_modules']`
+  - _Default_: `['**/node_modules/**', '**/dist/**', '**/build/**', '**/.intlayer/**', '**/.next/**', '**/.nuxt/**', '**/.expo/**', '**/.vercel/**', '**/.turbo/**', '**/.tanstack/**']`
   - _Description_: Directories excluded from content search.
   - _Note_: This setting is not yet used, but planned for future implementation.
 
@@ -556,15 +726,3 @@ Build options apply to the `@intlayer/babel` and `@intlayer/swc` plugins.
   - _Note_: Use this to limit optimization to relevant code files and improve build performance.
   - _Note_: This option will be ignored if `optimize` is disabled.
   - _Note_: Use glob pattern.
-
-## Doc History
-
-| Version | Date       | Changes                                                                                 |
-| ------- | ---------- | --------------------------------------------------------------------------------------- |
-| 6.0.2   | 2025-09-23 | Add `outputFormat` option                                                               |
-| 6.0.0   | 2025-09-21 | Remove `dictionaryOutput` field and `i18nextResourcesDir` field                         |
-| 6.0.0   | 2025-09-16 | Add `live` import mode                                                                  |
-| 6.0.0   | 2025-09-04 | Replace `hotReload` field by `liveSync` and add `liveSyncPort` and `liveSyncURL` fields |
-| 5.6.1   | 2025-07-25 | Replace `activateDynamicImport` with `importMode` option                                |
-| 5.6.0   | 2025-07-13 | Change default contentDir from `['src']` to `['.']`                                     |
-| 5.5.11  | 2025-06-29 | Add `docs` commands                                                                     |

package/docs/en/dictionary/condition.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - condition
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Conditional Content / Condition in Intlayer
@@ -231,9 +235,3 @@ For more detailed information on configuration and usage, refer to the following
 - [Next Intlayer Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_15.md)
 
 These resources offer further insights into the setup and usage of Intlayer across various environments and frameworks.
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/dictionary/content_file.md

@@ -11,6 +11,16 @@ slugs:
   - doc
   - concept
   - content
+history:
+  - version: 7.0.0
+    date: 2025-10-23
+    changes: Rename `autoFill` to `fill`
+  - version: 6.0.0
+    date: 2025-09-20
+    changes: Add fields documentation
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Content File
@@ -402,32 +412,33 @@ Transforms the dictionary into a per-locale dictionary where each field declared
 }
 ```
 
-#### `autoFill` (AutoFill)
+#### `fill` (Fill)
 
 Instructions for automatically filling dictionary content from external sources. This can be configured globally in `intlayer.config.ts` or per-dictionary. Supports multiple formats:
 
-- **`true`**: Enable auto-fill for all locales
+- **`true`**: Enable filling for all locales
+- **`false`**: Disable filling for all locales
 - **`string`**: Path to a single file or template with variables
 - **`object`**: Per-locale file paths
 
 **Examples:**
 
 ```json
-// Enable for all locales
+// Disable filling
 {
-  "autoFill": true
+  "fill": false
 }
 // Single file
 {
-  "autoFill": "./translations/aboutPage.content.json"
+  "fill": "./translations/aboutPage.content.json"
 }
 // Template with variables
 {
-  "autoFill": "/messages/{{locale}}/{{key}}/{{fileName}}.content.json"
+  "fill": "/messages/{{locale}}/{{key}}/{{fileName}}.content.json"
 }
 // Fine per-locale configuration
 {
-  "autoFill": {
+  "fill": {
     "en": "./translations/en/aboutPage.content.json",
     "fr": "./translations/fr/aboutPage.content.json",
     "es": "./translations/es/aboutPage.content.json"
@@ -441,7 +452,7 @@ Instructions for automatically filling dictionary content from external sources.
 - `{{fileName}}` – File name (e.g. `example`)
 - `{{key}}` – Dictionary key (e.g. `example`)
 
-> See [Auto-Fill Configuration in Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/autoFill.md) for more information.
+> See [Auto-Fill Configuration in Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/fill.md) for more information.
 
 ##### `priority` (number)
 
@@ -494,6 +505,10 @@ JSON schema used for validation of the dictionary structure. Automatically added
 
 For remote dictionaries, this is the unique identifier of the dictionary in the remote server. Used for fetching and managing remote content.
 
+##### `projectIds` (string[])
+
+For remote dictionaries, this array contains the IDs of the projects that can use this dictionary. A remote dictionary can be shared between multiple projects.
+
 ##### `localId` (LocalDictionaryId)
 
 Unique identifier for local dictionaries. Auto-generated by Intlayer to help identify the dictionary and determine if it's local or remote, along with its location.
@@ -510,7 +525,7 @@ The file path of the local dictionary, indicating which `.content` file the dict
 
 For remote dictionaries, this array contains all available versions of the dictionary. Helps track which versions are available for use.
 
-##### `autoFilled` (true)
+##### `filled` (true)
 
 Indicates whether the dictionary has been auto-filled from external sources. In case of conflicts, base dictionaries will override auto-filled dictionaries.
 
@@ -1039,16 +1054,9 @@ module.exports = {
    - Keep related content together in the same dictionary
    - Use nested objects to organize complex content structures
    - Leverage tags for categorization
-   - Use the `autoFill` to automatically fill the missing translations
+   - Use the `fill` to automatically fill the missing translations
 
 3. **Performance**:
    - Ajust the content configuration to limit the scope of watched files
    - Use live dictionaries only when real-time updates are necessary, (e.g. A/B testing, etc.)
    - Ensure the build transformation plugin (`@intlayer/swc`, or `@intlayer/babel`) is enabled to optimize the dictionary at build time
-
-## Doc History
-
-| Version | Date       | Changes                  |
-| ------- | ---------- | ------------------------ |
-| 6.0.0   | 2025-09-20 | Add fields documentation |
-| 5.5.10  | 2025-06-29 | Init history             |

package/docs/en/dictionary/enumeration.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - enumeration
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Enumeration / Plurielisation
@@ -239,9 +243,3 @@ For more detailed information on configuration and usage, refer to the following
 - [Next Intlayer Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_15.md)
 
 These resources provide further insights into the setup and usage of Intlayer in different environments and with various frameworks.
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |