@intlayer/docs 6.1.6 → 7.0.0-canary.1

package/docs/en/dictionary/file.md

@@ -16,13 +16,19 @@ slugs:
   - concept
   - content
   - file
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # File Content / Embedding Files in Intlayer
 
-## How File Embedding Works
+In Intlayer, the `file` function allows embedding external file content into a dictionary. This approach ensures that Intlayer recognizes the source file, enabling seamless integration with the Intlayer Visual Editor and CMS.
 
-In Intlayer, the `file` function allows embedding external file content into a dictionary. This approach ensures that Intlayer recognizes the source file, enabling seamless integration with the Intlayer Visual Editor and CMS. Unlike direct `import`, `require`, or `fs` file reading methods, using `file` associates the file with the dictionary, allowing Intlayer to track and update the content dynamically when the file is edited.
+## Why using `file` instead of `import`, `require`, or `fs`?
+
+Unlike `import`, `require`, or `fs` file reading methods, using `file` associates the file with the dictionary, allowing Intlayer to track and update the content dynamically when the file is edited. As a result, using file will offer better integration with the Intlayer Visual Editor and CMS.
 
 ## Setting Up File Content
 
@@ -197,6 +203,14 @@ const myMultilingualContent = {
 
 This setup allows the content to be dynamically retrieved based on the user's language preference. When used in the Intlayer Visual Editor or CMS, the system will recognize that the content comes from the specified Markdown files and ensure they remain editable.
 
+## Different types of paths
+
+When using the `file` function, you can use different types of paths to specify the file to embed.
+
+- `file("./path/to/file.txt")` - Relative path to the current file
+- `file("path/to/file.txt")` - Relative path to the project root directory
+- `file("/users/username/path/to/file.txt")` - Absolute path
+
 ## How Intlayer Handles File Content
 
 The `file` function is based on Node.js' `fs` module to read the content of the specified file and insert it into the dictionary. When used in conjunction with the Intlayer Visual Editor or CMS, Intlayer can track the relationship between the dictionary and the file. This allows Intlayer to:
@@ -216,9 +230,3 @@ For more details on configuring and using file embedding in Intlayer, refer to t
 - [Translation Content Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/translation.md)
 
 These resources provide further insights into file embedding, content management, and Intlayer’s integration with various frameworks.
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/dictionary/function_fetching.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - function-fetching
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Function Fetching
@@ -208,9 +212,3 @@ const MyComponent = () => {
 
 module.exports = MyComponent;
 ```
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/dictionary/gender.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - gender
+history:
+  - version: 5.7.2
+    date: 2025-07-27
+    changes: Introduce gender based content
 ---
 
 # Gender-Based Content / Gender in Intlayer
@@ -267,9 +271,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.7.2   | 2025-07-27 | Introduce gender based content |

package/docs/en/dictionary/insertion.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - insertion
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Insertion Content / Insertion in Intlayer
@@ -185,9 +189,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/markdown.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - markdown
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Markdown / Rich Text Content
@@ -373,9 +377,3 @@ const IntlayerMarkdownProvider = ({ children }) => (
 - [markdown-to-jsx on npm](https://www.npmjs.com/package/markdown-to-jsx)
 
 These resources provide further insights into setting up and using Intlayer with various content types and frameworks.
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/dictionary/nesting.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - nesting
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Nesting / Sub Content Referencing
@@ -267,9 +271,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 |

package/docs/en/dictionary/translation.md

@@ -16,6 +16,10 @@ slugs:
   - concept
   - content
   - translation
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Translation
@@ -303,9 +307,3 @@ module.exports = {
   }
 }
 ```
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/formatters.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-13
-updatedAt: 2025-08-20
+updatedAt: 2025-10-14
 title: Formatters
 description: Locale-aware formatting utilities based on Intl for numbers, percentages, currency, dates, relative time, units, and compact notation. Includes a cached Intl helper.
 keywords:
@@ -18,6 +18,28 @@ keywords:
 slugs:
   - doc
   - formatters
+history:
+  - version: 6.2.0
+    date: 2025-10-14
+    changes: Remove getIntlayerAsync from formatters
+  - version: 5.8.0
+    date: 2025-08-20
+    changes: Add vue formatters
+  - version: 5.8.0
+    date: 2025-08-18
+    changes: Add formatters documentation
+  - version: 5.8.0
+    date: 2025-08-20
+    changes: Add list formatter documentation
+  - version: 5.8.0
+    date: 2025-08-20
+    changes: Add additional Intl utilities (DisplayNames, Collator, PluralRules)
+  - version: 5.8.0
+    date: 2025-08-20
+    changes: Add locale utilities (getLocaleName, getLocaleLang, getLocaleFromPath, etc.)
+  - version: 5.8.0
+    date: 2025-08-20
+    changes: Add content handling utilities (getContent, getTranslation, getIntlayer, etc.)
 ---
 
 # Intlayer Formatters
@@ -46,10 +68,8 @@ import {
   getLocalizedUrl,
   getHTMLTextDir,
   getContent,
-  getLocalisedContent,
   getTranslation,
   getIntlayer,
-  getIntlayerAsync,
 } from "intlayer";
 ```
 
@@ -256,26 +276,6 @@ const content = getContent(
 - **nodeProps**: Properties for the transformation context
 - **locale**: Optional locale (defaults to configured default locale)
 
-### `getLocalisedContent(node, locale, nodeProps, fallback?)`
-
-Transforms a content node with only the translation plugin:
-
-```ts
-import { getLocalisedContent } from "intlayer";
-
-const content = getLocalisedContent(
-  contentNode,
-  "fr",
-  { dictionaryKey: "common" },
-  true // fallback to default locale if translation missing
-);
-```
-
-- **node**: The content node to transform
-- **locale**: The locale to use for translation
-- **nodeProps**: Properties for the transformation context
-- **fallback**: Whether to fallback to default locale (defaults to false)
-
 ### `getTranslation(languageContent, locale?, fallback?)`
 
 Extracts content for a specific locale from a language content object:
@@ -313,20 +313,6 @@ const nestedContent = getIntlayer("common", "fr", customPlugins);
 - **locale**: Optional locale (defaults to configured default locale)
 - **plugins**: Optional array of custom transformation plugins
 
-### `getIntlayerAsync(dictionaryKey, locale?, plugins?)`
-
-Asynchronously retrieves content from a distant dictionary:
-
-```ts
-import { getIntlayerAsync } from "intlayer";
-
-const content = await getIntlayerAsync("common", "fr");
-```
-
-- **dictionaryKey**: The key of the dictionary to retrieve
-- **locale**: Optional locale (defaults to configured default locale)
-- **plugins**: Optional array of custom transformation plugins
-
 ## Formatters
 
 All helpers below are exported from `intlayer`.
@@ -507,10 +493,8 @@ import {
   getLocalizedUrl,
   getHTMLTextDir,
   getContent,
-  getLocalisedContent,
   getTranslation,
   getIntlayer,
-  getIntlayerAsync,
 } from "intlayer";
 ```
 
@@ -605,14 +589,3 @@ import {
 ```
 
 > That composables will consider the locale from the injected `IntlayerProvider`
-
-## Doc History
-
-| Version | Date       | Changes                                                                        |
-| ------- | ---------- | ------------------------------------------------------------------------------ |
-| 5.8.0   | 2025-08-20 | Add vue formatters                                                             |
-| 5.8.0   | 2025-08-18 | Add formatters documentation                                                   |
-| 5.8.0   | 2025-08-20 | Add list formatter documentation                                               |
-| 5.8.0   | 2025-08-20 | Add additional Intl utilities (DisplayNames, Collator, PluralRules)            |
-| 5.8.0   | 2025-08-20 | Add locale utilities (getLocaleName, getLocaleLang, getLocaleFromPath, etc.)   |
-| 5.8.0   | 2025-08-20 | Add content handling utilities (getContent, getTranslation, getIntlayer, etc.) |

package/docs/en/how_works_intlayer.md

@@ -13,6 +13,10 @@ slugs:
   - doc
   - concept
   - how-works-intlayer
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # How Intlayer Works
@@ -88,7 +92,7 @@ For externalized dictionaries using the CMS, Intlayer performs a basic fetch ope
 
 Intlayer also provides a visual editor to allow you to edit your content in a visual way. This [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md) is available in the external `intlayer-editor` package.
 
-![visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/assets/visual_editor.gif)
+![visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/assets/visual_editor.gif?raw=true)
 
 - The server is a simple Express application that listens to requests from the client and retreives the content of your application, such as the `dictionaries` and the configuration to make it accessible on the client side.
 - On the other hand, the client is a React application that is used to interact with your content using a visual interface.
@@ -246,9 +250,3 @@ The `@intlayer/backend` package exports backend types and will eventually offer
 ## Chat with our smart documentation
 
 - [Ask your questions to our smart documentation](https://intlayer.org/doc/chat)
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/index.md

@@ -16,6 +16,10 @@ keywords:
 slugs:
   - doc
   - index
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Intlayer Documentation
@@ -167,9 +171,3 @@ Seamlessly integrate with **Next.js**:
 We value the power of open-source and community-driven development. If you’d like to propose improvements, add a new guide, or correct any issues in our docs, feel free to submit a Pull Request or open an issue on our [GitHub repository](https://github.com/aymericzip/intlayer/blob/main/docs/docs).
 
 **Ready to translate your application faster and more efficiently?** Dive into our docs to start using Intlayer today. Experience a robust, streamlined approach to internationalization that keeps your content organized and your team more productive.
-
-## Doc History
-
-| Version | Date       | Changes      |
-| ------- | ---------- | ------------ |
-| 5.5.10  | 2025-06-29 | Init history |

package/docs/en/interest_of_intlayer.md

@@ -12,6 +12,13 @@ keywords:
 slugs:
   - doc
   - why
+history:
+  - version: 5.8.0
+    date: 2025-08-19
+    changes: Update comparative table
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Why you should consider Intlayer?
@@ -280,10 +287,3 @@ GitHub stars are a strong indicator of a project's popularity, community trust,
 Using `intlayer`, you can declare your content in the format of your favorite i18n library, and intlayer will generate your namespaces in the location of your choice (example: `/messages/{{locale}}/{{namespace}}.json`).
 
 Refer to [`dictionaryOutput` and `i18nextResourcesDir` options](https://intlayer.org/doc/concept/configuration#content-configuration) for more details.
-
-## Document History
-
-| Version | Date       | Changes                  |
-| ------- | ---------- | ------------------------ |
-| 5.8.0   | 2025-08-19 | Update comparative table |
-| 5.5.10  | 2025-06-29 | Init history             |

package/docs/en/intlayer_CMS.md

@@ -17,6 +17,16 @@ slugs:
   - concept
   - cms
 youtubeVideo: https://www.youtube.com/watch?v=UDDTnirwi_4
+history:
+  - version: 6.0.1
+    date: 2025-09-22
+    changes: Add live sync documentation
+  - version: 6.0.0
+    date: 2025-09-04
+    changes: Replace `hotReload` field by `liveSync`
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Intlayer Content Management System (CMS) Documentation
@@ -31,11 +41,11 @@ For that, Intlayer introduce the concept of 'distant dictionaries'.
 
 ## Understanding distant dictionaries
 
-Intlayer make a difference between 'local' and 'distant' dictionaries.
+Intlayer make a difference between 'local' and 'remote' dictionaries.
 
 - A 'local' dictionary is a dictionary that is declared in your Intlayer project. Such as the declaration file of a button, or your navigation bar. Externalizing your content do not make sense in this case because this content is not supposed to change often.
 
-- A 'distant' dictionary is a dictionary that is managed through the Intlayer CMS. It could be useful to allow your team to manage your content in direct on your website, and also aims to use A/B testing features and SEO automatic optimization.
+- A 'remote' dictionary is a dictionary that is managed through the Intlayer CMS. It could be useful to allow your team to manage your content in direct on your website, and also aims to use A/B testing features and SEO automatic optimization.
 
 ## Visual editor vs CMS
 
@@ -260,8 +270,6 @@ Then you will be able to see and manage your dictionary in the [Intlayer CMS](ht
 
 Live Sync lets your app reflect CMS content changes at runtime. No rebuild or redeploy required. When enabled, updates are streamed to a Live Sync server that refreshes the dictionaries your application reads.
 
-> Live Sync requires a continuous server connection and is available on the enterprise plan.
-
 Enable Live Sync by updating your Intlayer configuration:
 
 ```typescript fileName="intlayer.config.ts" codeFormat="typescript"
@@ -533,11 +541,3 @@ If you encounter any issues with the CMS, check the following:
 - Ensure that the project configuration was pushed to the Intlayer CMS.
 
 - The visual editor use an iframe to display your website. Ensure that the Content Security Policy (CSP) of your website allows the CMS url as `frame-ancestors` ('https://intlayer.org' by default). Check the editor console for any error.
-
-## Doc History
-
-| Version | Date       | Changes                                 |
-| ------- | ---------- | --------------------------------------- |
-| 6.0.1   | 2025-09-22 | Add live sync documentation             |
-| 6.0.0   | 2025-09-04 | Replace `hotReload` field by `liveSync` |
-| 5.5.10  | 2025-06-29 | Init history                            |

package/docs/en/intlayer_cli.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-09-26
+updatedAt: 2025-01-27
 title: CLI
 description: Discover how to use the Intlayer CLI to manage your multilingual website. Follow the steps in this online documentation to set up your project in a few minutes.
 keywords:
@@ -16,6 +16,34 @@ slugs:
   - doc
   - concept
   - cli
+history:
+  - version: 6.1.4
+    date: 2025-01-27
+    changes: Add aliases for CLI arguments and commands
+  - version: 6.1.3
+    date: 2025-10-05
+    changes: Add build option to commands
+  - version: 6.1.2
+    date: 2025-09-26
+    changes: Add version command
+  - version: 6.1.0
+    date: 2025-09-26
+    changes: Set verbose option to default to true using CLI
+  - version: 6.1.0
+    date: 2025-09-23
+    changes: Add watch command and with option
+  - version: 6.0.1
+    date: 2025-09-23
+    changes: Add editor command
+  - version: 6.0.0
+    date: 2025-09-17
+    changes: Add content test and list command
+  - version: 5.5.11
+    date: 2025-07-11
+    changes: Update CLI command parameters documentation
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Intlayer CLI
@@ -157,6 +185,10 @@ If [intlayer editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/
 
   > Example: `npx intlayer dictionary push -d my-dictionary-id my-other-dictionary-id`
 
+- **`--dictionary`**: ids of the dictionaries to pull (alias for --dictionaries).
+
+  > Example: `npx intlayer dictionary push --dictionary my-dictionary-id my-other-dictionary-id`
+
 **Configuration options:**
 
 - **`--base-dir`**: Specify the base directory for the project. To retrieve the intlayer configuration, the command will look for the `intlayer.config.{ts,js,json,cjs,mjs}` file in the base directory.
@@ -186,6 +218,10 @@ If [intlayer editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/
 
   > Example: `npx intlayer dictionary push --keep-locale-dictionary`
 
+**Preparation options:**
+
+- **`--build`**: Build the dictionaries before pushing to ensure the content is up to date. True will force the build, false will skip the build, undefined will allow using the cache of the build.
+
 **Log options:**
 
 - **`--verbose`**: Enable verbose logging for debugging. (default to true using CLI)
@@ -225,6 +261,10 @@ If [intlayer editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/
 
   > Example: `npx intlayer dictionary pull -d my-dictionary-id my-other-dictionary-id`
 
+- **`--dictionary`**: Ids of the dictionaries to pull (alias for --dictionaries).
+
+  > Example: `npx intlayer dictionary pull --dictionary my-dictionary-id my-other-dictionary-id`
+
 **Configuration options:**
 
 - **`--base-dir`**: Specify the base directory for the project. To retrieve the intlayer configuration, the command will look for the `intlayer.config.{ts,js,json,cjs,mjs}` file in the base directory.
@@ -281,10 +321,18 @@ This command analyzes your content declaration files for potential issues such a
 
   > Example: `npx intlayer dictionary fill -k key1 key2`
 
+- **`--key [keys...]`**: Filter dictionaries based on keys (alias for --keys).
+
+  > Example: `npx intlayer dictionary fill --key key1 key2`
+
 - **`--excluded-keys [excludedKeys...]`**: Filter out dictionaries based on keys. If not provided, all dictionaries will be audited.
 
   > Example: `npx intlayer dictionary fill --excluded-keys key1 key2`
 
+- **`--excluded-key [excludedKeys...]`**: Filter out dictionaries based on keys (alias for --excluded-keys).
+
+  > Example: `npx intlayer dictionary fill --excluded-key key1 key2`
+
 - **`--path-filter [pathFilters...]`**: Filter dictionaries based on glob pattern for file paths.
 
   > Example: `npx intlayer dictionary fill --path-filter "src/home/**"`
@@ -336,6 +384,12 @@ This command analyzes your content declaration files for potential issues such a
 
   > Example: `npx intlayer fill --base-dir ./src`
 
+**Preparation options:**
+
+- **`--build`**: Build the dictionaries before pushing to ensure the content is up to date. True will force the build, false will skip the build, undefined will allow using the cache of the build.
+
+- **`--skip-metadata`**: Skip filling missing metadata (description, title, tags) for dictionaries.
+
 **Log options:**
 
 - **`--verbose`**: Enable verbose logging for debugging. (default to true using CLI)
@@ -354,6 +408,10 @@ This command will translate content from English to French and Spanish for all c
 npx intlayer content test
 ```
 
+##### Aliases:
+
+- `npx intlayer test`
+
 This command analyzes your content declaration files to identify missing translations across all configured locales. It provides a comprehensive report showing which translation keys are missing for which locales, helping you maintain consistency across your multilingual content.
 
 ##### Example output:
@@ -382,6 +440,10 @@ Total missing required locales: 0
 
   > Example: `npx intlayer content test --base-dir ./src --env-file .env.production.local`
 
+**Preparation options:**
+
+- **`--build`**: Build the dictionaries before pushing to ensure the content is up to date. True will force the build, false will skip the build, undefined will allow using the cache of the build.
+
 **Log options:**
 
 - **`--verbose`**: Enable verbose logging for debugging. (default to true using CLI)
@@ -420,6 +482,10 @@ The output helps you quickly identify which translations need to be completed to
 npx intlayer content list
 ```
 
+##### Aliases:
+
+- `npx intlayer list`
+
 This command displays all content declaration files in your project, showing their dictionary keys and file paths. It's useful for getting an overview of all your content files and verifying that they are properly discovered by Intlayer.
 
 ##### Example:
@@ -631,6 +697,11 @@ If you activated one of the git options, the command will only review the part o
 }
 ```
 
+> **Note**: You can also use the shorter aliases:
+>
+> - `npx intlayer list` instead of `npx intlayer content list`
+> - `npx intlayer test` instead of `npx intlayer content test`
+
 ### Editor commands
 
 The `editor` command rewrap the `intlayer-editor` commands.
@@ -643,6 +714,30 @@ The `editor` command rewrap the `intlayer-editor` commands.
 }
 ```
 
+### Live Sync commands
+
+Live Sync lets your app reflect CMS content changes at runtime. No rebuild or redeploy required. When enabled, updates are streamed to a Live Sync server that refreshes the dictionaries your application reads. See [Intlayer CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md) for more details.
+
+```json fileName="package.json"
+"scripts": {
+  "intlayer:live:start": "npx intlayer live start --with 'next dev --turbopack'"
+}
+```
+
+##### Arguments:
+
+**Configuration options:**
+
+- **`--base-dir`**: Specify the base directory for the project. To retrieve the intlayer configuration, the command will look for the `intlayer.config.{ts,js,json,cjs,mjs}` file in the base directory.
+
+  > Example: `npx intlayer dictionary push --env-file .env.production.local`
+
+**Log options:**
+
+- **`--verbose`**: Enable verbose logging for debugging. (default to true using CLI)
+
+---
+
 ## CLI SDK
 
 The CLI SDK is a library that allows you to use the Intlayer CLI in your own code.
@@ -720,15 +815,3 @@ Sometimes a terminal restart is needed to recognize new commands.
 ```bash
 npx clear-npx-cache
 ```
-
-## Doc History
-
-| Version | Date       | Changes                                         |
-| ------- | ---------- | ----------------------------------------------- |
-| 6.1.2   | 2025-09-26 | Add version command                             |
-| 6.1.0   | 2025-09-26 | Set verbose option to default to true using CLI |
-| 6.1.0   | 2025-09-23 | Add watch command and with option               |
-| 6.0.1   | 2025-09-23 | Add editor command                              |
-| 6.0.0   | 2025-09-17 | Add content test and list command               |
-| 5.5.11  | 2025-07-11 | Update CLI command parameters documentation     |
-| 5.5.10  | 2025-06-29 | Init history                                    |

package/docs/en/intlayer_visual_editor.md

@@ -16,6 +16,19 @@ slugs:
   - concept
   - editor
 youtubeVideo: https://www.youtube.com/watch?v=UDDTnirwi_4
+history:
+  - version: 6.1.0
+    date: 2025-09-23
+    changes: Add with option on CLI
+  - version: 6.0.1
+    date: 2025-09-22
+    changes: Change behavior of the editor when the file extension is not `.json`
+  - version: 6.0.0
+    date: 2025-09-21
+    changes: Add reexported command
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Intlayer Visual Editor Documentation
@@ -24,7 +37,7 @@ youtubeVideo: https://www.youtube.com/watch?v=UDDTnirwi_4
 
 The Intlayer Visual Editor is a tool that will wrap your website to interact with your content declaration files using a visual editor.
 
-![Intlayer Visual Editor Interface](https://github.com/aymericzip/intlayer/blob/main/docs/assets/visual_editor.gif)
+![Intlayer Visual Editor Interface](https://github.com/aymericzip/intlayer/blob/main/docs/assets/visual_editor.gif?raw=true)
 
 The `intlayer-editor` package is based on Intlayer and is available for JavaScript applications, such as React (Create React App), Vite + React, and Next.js.
 
@@ -273,12 +286,3 @@ If you encounter any issues with the visual editor, check the following:
     - The application URL should match the one you set in the editor configuration (`applicationURL`).
 
 - The visual editor use an iframe to display your website. Ensure that the Content Security Policy (CSP) of your website allows the CMS url as `frame-ancestors` ('http://localhost:8000' by default). Check the editor console for any error.
-
-## Doc History
-
-| Version | Date       | Changes                                                              |
-| ------- | ---------- | -------------------------------------------------------------------- |
-| 6.1.0   | 2025-09-23 | Add with option on CLI                                               |
-| 6.0.1   | 2025-09-22 | Change behavior of the editor when the file extension is not `.json` |
-| 6.0.0   | 2025-09-21 | Add reexported command                                               |
-| 5.5.10  | 2025-06-29 | Init history                                                         |