@intlayer/docs 6.1.6-canary.0 → 7.0.0-canary.0

package/docs/en-GB/intlayer_with_vite+preact.md

@@ -1,7 +1,7 @@
 ---
 createdAt: 2025-04-18
 updatedAt: 2025-06-29
-title: Translate your Vite and Preact website (i18n)
+title: How to translate your Vite and Preact app – i18n guide 2025
 description: Discover how to make your Vite and Preact website multilingual. Follow the documentation to internationalise (i18n) and translate it.
 keywords:
   - Internationalisation
@@ -15,6 +15,10 @@ slugs:
   - environment
   - vite-and-preact
 applicationTemplate: https://github.com/aymericzip/intlayer-vite-preact-template
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Getting Started Internationalising (i18n) with Intlayer and Vite and Preact
@@ -1048,38 +1052,38 @@ const App = () => (
 module.exports = App;
 ```
 
-In parallel, you can also use the `intlayerMiddlewarePlugin` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
+In parallel, you can also use the `intlayerMiddleware` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
 
 ```typescript {3,7} fileName="vite.config.ts" codeFormat="typescript"
 import { defineConfig } from "vite";
 import preact from "@preact/preset-vite";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [preact(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [preact(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.mjs" codeFormat="esm"
 import { defineConfig } from "vite";
 import preact from "@preact/preset-vite";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [preact(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [preact(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.cjs" codeFormat="commonjs"
 const { defineConfig } = require("vite");
 const preact = require("@preact/preset-vite");
-const { intlayer, intlayerMiddlewarePlugin } = require("vite-intlayer");
+const { intlayer, intlayerMiddleware } = require("vite-intlayer");
 
 // https://vitejs.dev/config/
 module.exports = defineConfig({
-  plugins: [preact(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [preact(), intlayer(), intlayerMiddleware()],
 });
 ```
 
@@ -1614,9 +1618,9 @@ module.exports = { LocalizedLink, checkIsExternalLink };
 
 Intlayer uses module augmentation to gain the benefits of TypeScript and strengthen your codebase.
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png)
+![Autocompletion](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png?raw=true)
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png)
+![Translation error](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png?raw=true)
 
 Ensure your TypeScript configuration includes the autogenerated types.
 
@@ -1671,7 +1675,3 @@ For more details on how to use the extension, refer to the [Intlayer VS Code Ext
 To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md) or externalise your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md).
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/intlayer_with_vite+react.md

@@ -1,7 +1,7 @@
 ---
 createdAt: 2024-03-07
 updatedAt: 2024-03-07
-title: Getting Started with Intlayer in Vite + React
+title: How to translate your Vite and React app – i18n guide 2025
 description: Learn how to add internationalisation (i18n) to your Vite and React application using Intlayer. Follow this guide to make your app multilingual.
 keywords:
   - Internationalisation
@@ -17,6 +17,11 @@ slugs:
   - vite-and-react
 applicationTemplate: https://github.com/aymericzip/intlayer-vite-react-template
 youtubeVideo: https://www.youtube.com/watch?v=dS9L7uJeak4---
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
+---
 
 # Getting Started Internationalising (i18n) with Intlayer and Vite and React
 
@@ -1037,38 +1042,38 @@ const App = () => (
 );
 ```
 
-In parallel, you can also use the `intlayerMiddlewarePlugin` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
+In parallel, you can also use the `intlayerMiddleware` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
 
 ```typescript {3,7} fileName="vite.config.ts" codeFormat="typescript"
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react-swc";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [react(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [react(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.mjs" codeFormat="esm"
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react-swc";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [react(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [react(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.cjs" codeFormat="commonjs"
 const { defineConfig } = require("vite");
 const react = require("@vitejs/plugin-react-swc");
-const { intlayer, intlayerMiddlewarePlugin } = require("vite-intlayer");
+const { intlayer, intlayerMiddleware } = require("vite-intlayer");
 
 // https://vitejs.dev/config/
 module.exports = defineConfig({
-  plugins: [react(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [react(), intlayer(), intlayerMiddleware()],
 });
 ```
 
@@ -1632,9 +1637,9 @@ By integrating this `Link` component across your application, you maintain a coh
 
 Intlayer uses module augmentation to take advantage of TypeScript and make your codebase stronger.
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png)
+![Autocompletion](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png?raw=true)
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png)
+![Translation error](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png?raw=true)
 
 Ensure your TypeScript configuration includes the autogenerated types.
 
@@ -1681,7 +1686,3 @@ For more details on how to use the extension, refer to the [Intlayer VS Code Ext
 To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md) or externalise your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md).
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/intlayer_with_vite+solid.md

@@ -1,7 +1,7 @@
 ---
 createdAt: 2025-04-18
 updatedAt: 2025-06-29
-title: Translate your Vite and Solid website (i18n)
+title: How to translate your Vite and Solid app – i18n guide 2025
 description: Discover how to make your Vite and Solid website multilingual. Follow the documentation to internationalise (i18n) and translate it.
 keywords:
   - Internationalisation
@@ -15,6 +15,10 @@ slugs:
   - environment
   - vite-and-solid
 # applicationTemplate: https://github.com/aymericzip/intlayer-vite-solid-template
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Getting Started Internationalising (i18n) with Intlayer and Vite and Solid
@@ -278,7 +282,3 @@ For more details on how to use the extension, refer to the [Intlayer VS Code Ext
 To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md) or externalise your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md).
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/intlayer_with_vite+svelte.md

@@ -1,7 +1,7 @@
 ---
 createdAt: 2025-04-18
 updatedAt: 2025-06-29
-title: Translate your Vite and Svelte website (i18n)
+title: How to translate your Vite and Svelte app – i18n guide 2025
 description: Discover how to make your Vite and Svelte website multilingual. Follow the documentation to internationalise (i18n) and translate it.
 keywords:
   - Internationalisation
@@ -15,6 +15,10 @@ slugs:
   - environment
   - vite-and-svelte
 # applicationTemplate: https://github.com/aymericzip/intlayer-vite-svelte-template
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Getting Started Internationalising (i18n) with Intlayer and Vite and Svelte
@@ -276,7 +280,3 @@ For more details on how to use the extension, refer to the [Intlayer VS Code Ext
 To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md) or externalise your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md).
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/intlayer_with_vite+vue.md

@@ -1,7 +1,7 @@
 ---
 createdAt: 2025-04-18
 updatedAt: 2025-06-29
-title: Translate your Vite and Vue website (i18n)
+title: How to translate your Vite and Vue app – i18n guide 2025
 description: Discover how to make your Vite and Vue website multilingual. Follow the documentation to internationalise (i18n) and translate it.
 keywords:
   - Internationalisation
@@ -15,6 +15,10 @@ slugs:
   - environment
   - vite-and-vue
 applicationTemplate: https://github.com/aymericzip/intlayer-vite-vue-template
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Getting Started Internationalising (i18n) with Intlayer and Vite and Vue
@@ -672,38 +676,38 @@ import LocaleSwitcher from "@components/LocaleSwitcher.vue";
 </template>
 ```
 
-In parallel, you can also use the `intlayerMiddlewarePlugin` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
+In parallel, you can also use the `intlayerMiddleware` to add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.
 
 ```typescript {3,7} fileName="vite.config.ts" codeFormat="typescript"
 import { defineConfig } from "vite";
 import vue from "@vitejs/plugin-vue";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [vue(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [vue(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.mjs" codeFormat="esm"
 import { defineConfig } from "vite";
 import vue from "@vitejs/plugin-vue";
-import { intlayer, intlayerMiddlewarePlugin } from "vite-intlayer";
+import { intlayer, intlayerMiddleware } from "vite-intlayer";
 
 // https://vitejs.dev/config/
 export default defineConfig({
-  plugins: [vue(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [vue(), intlayer(), intlayerMiddleware()],
 });
 ```
 
 ```javascript {3,7} fileName="vite.config.cjs" codeFormat="commonjs"
 const { defineConfig } = require("vite");
 const vue = require("@vitejs/plugin-vue");
-const { intlayer, intlayerMiddlewarePlugin } = require("vite-intlayer");
+const { intlayer, intlayerMiddleware } = require("vite-intlayer");
 
 // https://vitejs.dev/config/
 module.exports = defineConfig({
-  plugins: [vue(), intlayer(), intlayerMiddlewarePlugin()],
+  plugins: [vue(), intlayer(), intlayerMiddleware()],
 });
 ```
 
@@ -721,9 +725,9 @@ To automatically update the URL when the user changes the language, you can modi
     </select>
   </div>
   const { defineConfig } = require("vite"); const vue =
-  require("@vitejs/plugin-vue"); const { intlayer, intlayerMiddlewarePlugin } =
+  require("@vitejs/plugin-vue"); const { intlayer, intlayerMiddleware } =
   require("vite-intlayer"); // https://vitejs.dev/config/ module.exports =
-  defineConfig({ plugins: [vue(), intlayer(), intlayerMiddlewarePlugin()], });
+  defineConfig({ plugins: [vue(), intlayer(), intlayerMiddleware()], });
 </template>
 ```
 
@@ -1062,9 +1066,9 @@ const { myMarkdownContent } = useIntlayer("my-component");
 
 Intlayer uses module augmentation to leverage the benefits of TypeScript and strengthen your codebase.
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png)
+![Autocompletion](https://github.com/aymericzip/intlayer/blob/main/docs/assets/autocompletion.png?raw=true)
 
-![alt text](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png)
+![Translation error](https://github.com/aymericzip/intlayer/blob/main/docs/assets/translation_error.png?raw=true)
 
 Ensure your TypeScript configuration includes the auto-generated types.
 
@@ -1133,7 +1137,3 @@ For more details on how to use the extension, refer to the [Intlayer VS Code Ext
 To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md) or externalise your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md).
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/introduction.md

@@ -12,6 +12,10 @@ keywords:
 slugs:
   - doc
   - get-started
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Intlayer Documentation
@@ -208,7 +212,3 @@ We value the power of open-source and community-driven development. If you’d l
 **Ready to translate your application faster and more efficiently?** Dive into our docs to start using Intlayer today. Experience a robust, streamlined approach to internationalisation that keeps your content organised and your team more productive.
 
 ---
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/locale_mapper.md

@@ -12,6 +12,10 @@ keywords:
 slugs:
   - doc
   - locale-mapper
+history:
+  - version: 5.7.2
+    date: 2025-07-27
+    changes: Add locale mapper documentation
 ---
 
 # Locale Mapper
@@ -236,9 +240,3 @@ The Locale Mapper seamlessly integrates with your Intlayer configuration:
 - **URL Prefixing**: Respects `configuration.middleware.prefixDefault`
 
 This ensures consistency across your application and reduces configuration duplication.
-
-## Doc History
-
-| Version | Date       | Changes                         |
-| ------- | ---------- | ------------------------------- |
-| 5.7.2   | 2025-07-27 | Add locale mapper documentation |

package/docs/en-GB/mcp_server.md

@@ -14,6 +14,19 @@ keywords:
 slugs:
   - doc
   - mcp-server
+history:
+  - version: 5.5.12
+    date: 2025-07-11
+    changes: Add set up of ChatGPT
+  - version: 5.5.12
+    date: 2025-07-10
+    changes: Add set up of Claude Desktop
+  - version: 5.5.12
+    date: 2025-07-10
+    changes: Add SSE transport and distant server
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initialise history
 ---
 
 # Intlayer MCP Server
@@ -197,12 +210,3 @@ npx @intlayer/mcp
 ```
 
 ---
-
-## Doc History
-
-| Version | Date       | Changes                              |
-| ------- | ---------- | ------------------------------------ |
-| 5.5.12  | 2025-07-11 | Add set up of ChatGPT                |
-| 5.5.12  | 2025-07-10 | Add set up of Claude Desktop         |
-| 5.5.12  | 2025-07-10 | Add SSE transport and distant server |
-| 5.5.10  | 2025-06-29 | Initialise history                   |

package/docs/en-GB/packages/express-intlayer/t.md

@@ -17,6 +17,10 @@ slugs:
   - packages
   - express-intlayer
   - t
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Documentation: `t` Function in `express-intlayer`
@@ -451,7 +455,3 @@ app.get("/morning", (_req, res) => {
 ## Conclusion
 
 The `t` function is a powerful tool for backend internationalisation. By using it effectively, you can create a more inclusive and user-friendly application for a global audience. For advanced usage and detailed configuration options, refer to the [documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/configuration.md).
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/packages/intlayer/getConfiguration.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getConfiguration
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Documentation: `getConfiguration` Function in `intlayer`
@@ -140,7 +144,3 @@ console.log(cookieName); // Output: "INTLAYER_LOCALE"
 ## Usage in Applications
 
 The `getConfiguration` function is a cornerstone utility for initialising and managing the configuration of an `intlayer` application. By providing access to settings like locales, middleware, and content directories, it ensures consistency and scalability across multilingual and content-driven applications.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/packages/intlayer/getEnumeration.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getEnumeration
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Documentation: `getEnumeration` Function in `intlayer`
@@ -158,7 +162,3 @@ console.log(content); // Output: "You have less than four"
 ## Notes
 
 - The `findMatchingCondition` utility is used to determine the appropriate condition based on the given quantity.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/packages/intlayer/getHTMLTextDir.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getHTMLTextDir
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getHTMLTextDir` Function in `intlayer`
@@ -117,7 +121,3 @@ const HTMLLayout = ({ children, locale }) => (
 ```
 
 In the example above, the `dir` attribute is dynamically set based on the locale.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/intlayer/getLocaleLang.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getLocaleLang
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getLocaleLang` Function in `intlayer`
@@ -77,7 +81,3 @@ getLocaleLang(Locales.FRENCH); // Output: "fr"
 
 - **Malformed Locale Strings:**
   - If the `locale` does not follow the `language-country` format (e.g., `Locales.ENGLISH-US`), the function safely returns the part before `'-'` or the entire string if no `'-'` is present.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/intlayer/getLocaleName.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getLocaleName
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getLocaleName` Function in `intlayer`
@@ -113,7 +117,3 @@ getLocaleName("unknown-locale"); // Output: "Unknown locale"
   - The function defaults to returning the `displayLocale`'s own name.
 - **Missing translations:**
   - If `localeNameTranslations` does not contain an entry for the `targetLocale` or the specific `displayLocale`, the function falls back to the `ownLocalesName` or returns `"Unknown locale"`.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/intlayer/getLocalizedUrl.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getLocalizedUrl
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Documentation: `getLocalizedUrl` Function in `intlayer`
@@ -241,7 +245,3 @@ getLocalizedUrl("/about", Locales.ENGLISH); // Output: "/about"
 ```
 
 By integrating `getLocalizedUrl`, developers can maintain consistent URL structures across multiple languages, enhancing both user experience and SEO.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/packages/intlayer/getMultilingualUrls.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getMultilingualUrls
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getMultilingualUrls` Function in `intlayer`
@@ -269,7 +273,3 @@ getMultilingualUrls(
 ```
 
 By integrating `getMultilingualUrls`, developers can maintain consistent URL structures across multiple languages, enhancing both user experience and SEO.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/intlayer/getPathWithoutLocale.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getPathWithoutLocale
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getPathWithoutLocale` Functions in `intlayer`
@@ -70,7 +74,3 @@ console.log(getPathWithoutLocale("/en/dashboard")); // Output: "/dashboard"
 console.log(getPathWithoutLocale("/fr/dashboard")); // Output: "/dashboard"
 console.log(getPathWithoutLocale("https://example.com/en/dashboard")); // Output: "https://example.com/dashboard"
 ```
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/intlayer/getTranslation.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - intlayer
   - getTranslation
+history:
+  - version: 5.5.10
+    date: 29-06-2025
+    changes: Initial history
 ---
 
 # Documentation: `getTranslationContent` Function in `intlayer`
@@ -223,7 +227,3 @@ console.log(customContent.greeting); // Output: "Bonjour"
   - If a locale is partially defined, the function does not merge contents. It strictly retrieves the value of the specified locale or falls back to the default.
 - **TypeScript Enforcement:**
   - If the locales in `languageContent` do not match the project configuration, TypeScript will enforce all required locales to be defined, ensuring the content is complete and type-safe.
-
-## Doc History
-
-- 5.5.10 - 29-06-2025: Initial history

package/docs/en-GB/packages/intlayer/getTranslationContent.md

@@ -17,6 +17,10 @@ slugs:
   - package
   - intlayer
   - getTranslationContent
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Initial history
 ---
 
 # Documentation: `getTranslation` Function in `intlayer`
@@ -198,7 +202,3 @@ console.log(customContent.greeting); // Output: "Bonjour"
   - If a locale is partially defined, the function does not merge contents. It strictly retrieves the value of the specified locale or falls back to the default.
 - \*\*TypeScript Enforcement::
   - If the locales in `languageContent` do not match the project configuration, TypeScript will enforce all required locales to be defined, ensuring the content is complete and type-safe.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Initial history

package/docs/en-GB/packages/next-intlayer/t.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - next-intlayer
   - t
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # Documentation: `t` Function in `next-intlayer`
@@ -354,7 +358,3 @@ For more detailed usage and advanced features, refer to the [next-intlayer docum
 ---
 
 **Note**: Remember to set up your `IntlayerClientProvider` and `IntlayerServerProvider` properly to ensure that the current locale is correctly passed down to your components. This is crucial for the `t` function to return the correct translations.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history

package/docs/en-GB/packages/next-intlayer/useDictionary.md

@@ -18,6 +18,10 @@ slugs:
   - packages
   - next-intlayer
   - useDictionary
+history:
+  - version: 5.5.10
+    date: 2025-06-29
+    changes: Init history
 ---
 
 # React Integration: `useDictionary` Hook Documentation
@@ -268,7 +272,3 @@ Unlike integrations using visual editors, attributes such as `buttonTitle.value`
 - **Localisation Updates**: When updating content, ensure all locales are consistent to avoid missing translations.
 
 This documentation focuses on the integration of the `useDictionary` hook, providing a streamlined approach to managing localised content without relying on visual editor functionalities.
-
-## Doc History
-
-- 5.5.10 - 2025-06-29: Init history