@intlayer/docs 9.4.3 → 9.5.0

package/docs/en-GB/migration_from_next-intl_to_intlayer.md

@@ -33,7 +33,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -41,25 +40,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimises your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -67,8 +62,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategy
 
 The recommended approach for existing apps is the **compat adapter**: install `@intlayer/next-intl`, which exposes the **exact same API** as `next-intl` but delegates all translation work to Intlayer under the hood.
@@ -77,20 +70,15 @@ You keep your existing `useTranslations`, `getTranslations`, `NextIntlClientProv
 
 Over time you can optionally migrate individual files to Intlayer's richer `.content.ts` format to unlock the visual editor, CMS, and per-component content scoping — but that step is entirely optional and can be done incrementally.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing `next-intl` app running on Intlayer with zero code changes.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the `@intlayer/next-intl` compat adapter:
@@ -134,7 +122,6 @@ bun add intlayer next-intlayer @intlayer/next-intl @intlayer/sync-json-plugin
 > Keep `next-intl` installed — it is still required for **URL routing** (`createNavigation`, `createMiddleware`, `Link`, `redirect`, `usePathname`, `useRouter`). The compat adapter does **not** replace the routing layer.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -171,7 +158,6 @@ export default config;
 > For a complete list of configuration options, see the [configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).
 
 </Step>
-
 <Step number={3} title="Add the Intlayer Plugin to Next.js">
 
 Wrap your existing Next.js config with `createNextIntlPlugin` from `@intlayer/next-intl/plugin`. This wrapper composes `withIntlayer` **and** registers the `next-intl` → `@intlayer/next-intl` aliases for you:
@@ -212,14 +198,11 @@ That's it for the quick migration. Your app now runs on Intlayer while keeping e
 > t("counter.label"); // ✓ typed
 > ```
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The `createNextIntlPlugin()` wrapper already handles `next-intl` → `@intlayer/next-intl` aliasing at the bundler level. If you prefer to make the dependency explicit in your source files (and use the plain `withIntlayer` plugin instead), you can rename imports manually:
@@ -246,7 +229,6 @@ The `createNextIntlPlugin()` wrapper already handles `next-intl` → `@intlayer/
 > Alternatively, you can use `defineRouting` from `@intlayer/next-intl/routing` which merges locale config from your `intlayer.config.ts` automatically.
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, you can use its CLI to fill missing translations automatically using the LLM of your choice:
@@ -308,8 +290,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once `@intlayer/next-intl` is in place, the following `next-intl` boilerplate can be removed:
@@ -322,8 +302,6 @@ Once `@intlayer/next-intl` is in place, the following `next-intl` boilerplate ca
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place an `about.content.ts` file right next to your `about/page.tsx` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralised index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -338,8 +316,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -349,8 +325,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)

package/docs/en-GB/migration_from_nuxtjs_i18n_to_intlayer.md

@@ -34,7 +34,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -42,25 +41,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimises your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -68,8 +63,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategies
 
 Since `@nuxtjs/i18n` is powered by `vue-i18n` under the hood, there are two complementary strategies for migrating to Intlayer:
@@ -80,20 +73,15 @@ Since `@nuxtjs/i18n` is powered by `vue-i18n` under the hood, there are two comp
 
 This guide covers **Strategy 1** first (drop-in compat adapter), then walks through the optional full migration.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing Nuxt app running on Intlayer with zero code changes in your components.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the compat adapter:
@@ -137,7 +125,6 @@ bun add intlayer vue-intlayer nuxt-intlayer @intlayer/vue-i18n @intlayer/sync-js
 > You can safely keep `@nuxtjs/i18n` installed during migration, though you will remove it from your Nuxt config shortly.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -172,7 +159,6 @@ export default config;
 > **`source`** maps a locale to its JSON file path. **`location`** tells the Intlayer watcher which folder to monitor for changes. The `format: 'icu'` option ensures that placeholders are parsed correctly for `vue-i18n`.
 
 </Step>
-
 <Step number={3} title="Update Nuxt Configuration">
 
 Replace the `@nuxtjs/i18n` module with `nuxt-intlayer` in your `nuxt.config.ts`. The Intlayer plugin automatically injects module aliases, meaning your existing `import { useI18n } from 'vue-i18n'` calls are transparently redirected to `@intlayer/vue-i18n`.
@@ -192,14 +178,11 @@ export default defineNuxtConfig({
 
 That's it for the quick migration. Your Nuxt app now runs on Intlayer whilst keeping every `$t` and `useI18n()` intact.
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The Intlayer plugins already handle aliasing at the bundler level. If you prefer to make the dependency explicit in your source files, you can rename imports manually:
@@ -211,7 +194,6 @@ The Intlayer plugins already handle aliasing at the bundler level. If you prefer
 These are **drop-in replacements** — no changes to call signatures, arguments, or return types are required.
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, use its CLI to fill missing translations automatically:
@@ -273,8 +255,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once the compat adapter is in place, the following boilerplate can be removed:
@@ -287,8 +267,6 @@ Once the compat adapter is in place, the following boilerplate can be removed:
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place a `my-component.content.ts` file right next to your `MyComponent.vue` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralised index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -303,8 +281,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -314,8 +290,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)

package/docs/en-GB/migration_from_react-i18next_to_intlayer.md

@@ -34,7 +34,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -42,25 +41,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimises your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -68,8 +63,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategies
 
 There are two complementary strategies for migrating from `react-i18next` / `i18next` to Intlayer:
@@ -80,20 +73,15 @@ There are two complementary strategies for migrating from `react-i18next` / `i18
 
 This guide covers **Strategy 1** first (drop-in compat adapter), then walks through the optional full migration.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing `react-i18next` app running on Intlayer with zero code changes.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the compat adapters:
@@ -137,7 +125,6 @@ bun add intlayer react-intlayer @intlayer/react-i18next @intlayer/i18next @intla
 > You can keep `react-i18next` and `i18next` installed — the compat adapters use them as `devDependencies` / optional `peerDependencies` for TypeScript types. You don't need to change any `package.json` peers.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -172,7 +159,6 @@ export default config;
 > **`source`** maps a locale to its JSON file path. **`location`** tells the Intlayer watcher which folder to monitor for changes. The `format: 'i18next'` option ensures that placeholders like `{{name}}` are parsed correctly.
 
 </Step>
-
 <Step number={3} title="Add the Intlayer Plugin to your Bundler">
 
 Wrap your existing bundler config with the compat plugin. It composes the core Intlayer plugin, wires up content watching, and — critically — **injects module aliases** so that your existing `import … from 'react-i18next'` (and `'i18next'`) calls are transparently redirected to `@intlayer/react-i18next` / `@intlayer/i18next` at build time. No source file changes are needed.
@@ -233,14 +219,11 @@ That's it for the quick migration. Your app now runs on Intlayer while keeping e
 > tAbout("counter.label"); // ✓ typed
 > ```
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The Intlayer plugins already handle aliasing at the bundler level. If you prefer to make the dependency explicit in your source files, you can rename imports manually:
@@ -265,7 +248,6 @@ For Next.js (`next-i18next`):
 | `import { useTranslation } from 'next-i18next'`                                | `import { useTranslation } from '@intlayer/next-i18next'`         |
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, use its CLI to fill missing translations automatically:
@@ -327,8 +309,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once the compat adapters are in place, the following `react-i18next` / `i18next` boilerplate can be removed:
@@ -341,8 +321,6 @@ Once the compat adapters are in place, the following `react-i18next` / `i18next`
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place a `my-component.content.ts` file right next to your `MyComponent.tsx` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralised index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -357,8 +335,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -368,8 +344,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)

package/docs/en-GB/migration_from_vue-i18n_to_intlayer.md

@@ -33,7 +33,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -41,25 +40,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimises your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -67,8 +62,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategies
 
 There are two complementary strategies for migrating from `vue-i18n` to Intlayer:
@@ -79,20 +72,15 @@ There are two complementary strategies for migrating from `vue-i18n` to Intlayer
 
 This guide covers **Strategy 1** first (drop-in compat adapter), then walks through the optional full migration.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing `vue-i18n` app running on Intlayer with zero code changes in your components.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the compat adapter:
@@ -136,7 +124,6 @@ bun add intlayer vue-intlayer @intlayer/vue-i18n @intlayer/sync-json-plugin
 > You can keep `vue-i18n` installed — the compat adapter uses it as a `devDependency` / `peerDependency` for TypeScript types.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -171,7 +158,6 @@ export default config;
 > **`source`** maps a locale to its JSON file path. **`location`** tells the Intlayer watcher which folder to monitor for changes. The `format: 'icu'` option ensures that placeholders are parsed correctly for `vue-i18n`.
 
 </Step>
-
 <Step number={3} title="Add the Intlayer Plugin to your Bundler">
 
 Wrap your existing bundler config with the compat plugin. It composes the core Intlayer plugin, wires up content watching, and — critically — **injects a module alias** so that your existing `import … from 'vue-i18n'` calls are transparently redirected to `@intlayer/vue-i18n` at build time. No source file changes are needed.
@@ -222,14 +208,11 @@ That's it for the quick migration. Your app now runs on Intlayer while keeping e
 > t("does.not.exist"); // ✗ TypeScript error
 > ```
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The Intlayer plugins already handle aliasing at the bundler level. If you prefer to make the dependency explicit in your source files, you can rename imports manually:
@@ -242,7 +225,6 @@ The Intlayer plugins already handle aliasing at the bundler level. If you prefer
 These are **drop-in replacements** — no changes to call signatures, arguments, or return types are required.
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, use its CLI to fill missing translations automatically:
@@ -304,8 +286,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once the compat adapters are in place, the following `vue-i18n` boilerplate can be removed:
@@ -318,8 +298,6 @@ Once the compat adapters are in place, the following `vue-i18n` boilerplate can
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place a `my-component.content.ts` file right next to your `MyComponent.vue` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralised index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -334,8 +312,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -345,8 +321,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_visual_editor.md)

package/docs/en-GB/packages/@intlayer_babel/export.md

@@ -43,8 +43,6 @@ Import:
 import { ... } from "@intlayer/babel";
 ```
 
----
-
 ### Plugins
 
 | Function / Class               | Description                                                                                                                                                                                 |
@@ -57,8 +55,6 @@ import { ... } from "@intlayer/babel";
 | `makeUsageAnalyzerBabelPlugin` | Factory function that produces a Babel plugin to analyze the usage of `useIntlayer` / `getIntlayer` in the source code and aggregate field usage data in the shared `PruneContext`.         |
 | `getSharedPruneContext`        | Helper function that returns the shared `PruneContext` object for the specified base directory, or `null` if it has not been initialised yet.                                               |
 
----
-
 ### Plugin Configuration Utilities
 
 | Function                   | Description                                                                                                                                       |
@@ -68,8 +64,6 @@ import { ... } from "@intlayer/babel";
 | `getPurgePluginOptions`    | Loads the Intlayer configuration and returns `PurgePluginOptions` ready for use with `intlayerPurgeBabelPlugin`.                                  |
 | `getMinifyPluginOptions`   | Loads the Intlayer configuration and returns `MinifyPluginOptions` ready for use with `intlayerMinifyBabelPlugin`.                                |
 
----
-
 ### Types
 
 | Type                    | Description                                                                                                     |
@@ -87,8 +81,6 @@ import { ... } from "@intlayer/babel";
 | `CompatCallerConfig`    | Configuration for a compatible usage analyzer for compat-adapter packages (caller name and processing options). |
 | `ScriptBlock`           | Script block extracted from a SFC file (Vue or Svelte): content, start offset, and end offset.                  |
 
----
-
 ### Utility Functions
 
 | Function                          | Description                                                                                                                                                   |
@@ -100,8 +92,6 @@ import { ... } from "@intlayer/babel";
 | `BABEL_PARSER_OPTIONS`            | Constant representing Babel parser options covering the supported frameworks (React/Vue/Svelte/Angular/...).                                                  |
 | `INTLAYER_CALLER_NAMES`           | Constant list of original Intlayer caller names: `['useIntlayer', 'getIntlayer']`.                                                                            |
 
----
-
 ## Example Usage
 
 ```js

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

@@ -27,14 +27,10 @@ author: aymericzip
 
 The `t` function in the `adonis-intlayer` package is the core utility for providing localised responses in your AdonisJS application. It simplifies internationalisation (i18n) by dynamically selecting content based on the user's preferred language.
 
----
-
 ## Overview
 
 The `t` function is used to define and retrieve translations for a given set of languages. It automatically determines the appropriate language to return based on the client's request settings, such as the `Accept-Language` header. If the preferred language is unavailable, it gracefully falls back to the default locale specified in your configuration.
 
----
-
 ## Key Features
 
 - **Dynamic Localisation**: Automatically selects the most appropriate translation for the client.
@@ -42,8 +38,6 @@ The `t` function is used to define and retrieve translations for a given set of
 - **Asynchronous Context**: Works seamlessly within the AdonisJS request lifecycle using Async Local Storage.
 - **TypeScript Support**: Enforce type safety for your translations.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +52,6 @@ t(translations: Record<string, any>): any;
 
 - The content representing the client's preferred language.
 
----
-
 ## Loading the Middleware
 
 To ensure that the `t` function works correctly, you **must** register the `intlayer` middleware in your AdonisJS application.
@@ -68,8 +60,6 @@ To ensure that the `t` function works correctly, you **must** register the `intl
 router.use([() => import("adonis-intlayer/middleware")]);
 ```
 
----
-
 ## Usage Examples
 
 ### Basic Example
@@ -105,8 +95,6 @@ export default class ExampleController {
 }
 ```
 
----
-
 ## Advanced Topics
 
 ### Fallback Mechanism