@intlayer/docs 7.0.7 → 7.0.8-canary.0

package/blog/en/intlayer_with_i18next.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-12-24
-updatedAt: 2025-11-01
+updatedAt: 2025-11-06
 title: How to automate your i18next JSON translations using Intlayer
 description: Automate your JSON translations with Intlayer and i18next for enhanced internationalization in JavaScript applications.
 keywords:
@@ -20,6 +20,9 @@ slugs:
   - blog
   - intlayer-with-i18next
 history:
+  - version: 7.0.7
+    date: 2025-11-06
+    changes: Add AI provider support doc
   - version: 7.0.6
     date: 2025-11-01
     changes: Add loadJSON plugin
@@ -38,16 +41,25 @@ See a concrete comparison with i18next in our [next-i18next vs. next-intl vs. In
 
 ## Why Combine Intlayer with i18next?
 
-While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with i18next for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with i18next for several reasons.
 
-1. **Existing codebase**: You have an established i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with i18next but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for i18next to help automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with i18next.
+However, **i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **i18next**, you get the best of both worlds — i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for i18next**, allowing you to:
+
+- Gradually migrate from i18next to Intlayer.
+- Keep existing i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 
@@ -159,6 +171,57 @@ This will load all the JSON files in the `src` directory that match the pattern
 
 ---
 
+### Step 4: Set up AI provider
+
+Intlayer unlocks a set of advanced automation and developer-friendly features for your i18next workflow.
+
+- **Automatic detection and filling of missing translations**: Intlayer scans your JSON dictionaries, finds untranslated or missing keys, and translates only those, so 99% of your JSON remains untouched.
+- **Chunked translation for large JSON files**: When your translation files are very large, Intlayer automatically splits processing into manageable chunks, translating them independently to avoid API limits and memory issues.
+- **Namespace parallelization**: If you have hundreds of namespaces (or files), Intlayer parallelizes the translation tasks, efficiently speeding up your CI/CD or bulk translation operations.
+- **Flexible AI provider support**: Choose your preferred AI provider (e.g., OpenAI, Claude, Gemini), simply by configuring credentials. Use your own API key, and switch providers as needed.
+- **Resilient AI response handling**: Intlayer can handle edge cases where your AI provider returns text as either a string or an object, even auto-retrying when the format is inconsistent.
+- **CLI & CI/CD ready**: Run Intlayer’s checks and auto-filling directly in your tests or pipelines, making your localization process robust and automated.
+- **Integrates on top of your existing setup**: You don’t need to change your i18next or Next.js foundation. Intlayer works as an add-on plugin to your current setup, giving you all of these benefits with minimal migration.
+
+Here is an example of how to set up the AI provider:
+
+```ts fileName="intlayer.config.ts"
+import { Locales, type IntlayerConfig } from "intlayer";
+import { loadJSON, syncJSON } from "@intlayer/sync-json-plugin";
+
+const config: IntlayerConfig = {
+  internationalization: {
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
+  },
+  ai: {
+    provider: "openai",
+    model: "gpt-5-mini",
+    apiKey: process.env.OPENAI_API_KEY,
+  },
+  plugins: [
+    syncJSON({
+      source: ({ key, locale }) => `./locales/${locale}/${key}.json`,
+    }),
+  ],
+};
+
+export default config;
+```
+
+Then you can execute the following command to fill your translations:
+
+```bash
+npx intlayer fill
+```
+
+This will fill your translations with the AI provider you have configured.
+
+> See all the available AI providers in the [Intlayer AI configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md#ai-configuration).
+> See all the available commands in the [Intlayer CLI documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_cli.md).
+
+---
+
 ## Git Configuration
 
 It's recommended to ignore auto-generated Intlayer files:

package/blog/en/intlayer_with_next-i18next.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-10-29
+updatedAt: 2025-11-06
 title: Intlayer and next-i18next
 description: Integrate Intlayer with next-i18next for a comprehensive Next.js internationalization solution
 keywords:
@@ -16,6 +16,9 @@ slugs:
   - blog
   - intlayer-with-next-i18next
 history:
+  - version: 7.0.7
+    date: 2025-11-06
+    changes: Add AI provider support doc
   - version: 7.0.6
     date: 2025-11-01
     changes: Add loadJSON plugin
@@ -24,7 +27,7 @@ history:
     changes: Change to syncJSON plugin and comprehensive rewrite
 ---
 
-# Next.js Internationalization (i18n) with next-i18next and Intlayer
+# How to automate your next-i18next JSON translations using Intlayer
 
 ## Table of Contents
 
@@ -40,14 +43,23 @@ See a concrete comparison with next-intl in our [next-i18next vs. next-intl vs.
 
 While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with next-i18next for several reasons:
 
-1. **Existing codebase**: You have an established next-i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with next-i18next but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for next-i18next to help automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with next-i18next.
+However, **i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **i18next**, you get the best of both worlds — i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for i18next**, allowing you to:
+
+- Gradually migrate from i18next to Intlayer.
+- Keep existing i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ---
 
@@ -159,6 +171,57 @@ This will load all the JSON files in the `src` directory that match the pattern
 
 ---
 
+### Step 4: Set up AI provider
+
+Intlayer unlocks a set of advanced automation and developer-friendly features for your i18next workflow.
+
+- **Automatic detection and filling of missing translations**: Intlayer scans your JSON dictionaries, finds untranslated or missing keys, and translates only those, so 99% of your JSON remains untouched.
+- **Chunked translation for large JSON files**: When your translation files are very large, Intlayer automatically splits processing into manageable chunks, translating them independently to avoid API limits and memory issues.
+- **Namespace parallelization**: If you have hundreds of namespaces (or files), Intlayer parallelizes the translation tasks, efficiently speeding up your CI/CD or bulk translation operations.
+- **Flexible AI provider support**: Choose your preferred AI provider (e.g., OpenAI, Claude, Gemini), simply by configuring credentials. Use your own API key, and switch providers as needed.
+- **Resilient AI response handling**: Intlayer can handle edge cases where your AI provider returns text as either a string or an object, even auto-retrying when the format is inconsistent.
+- **CLI & CI/CD ready**: Run Intlayer’s checks and auto-filling directly in your tests or pipelines, making your localization process robust and automated.
+- **Integrates on top of your existing setup**: You don’t need to change your i18next or Next.js foundation. Intlayer works as an add-on plugin to your current setup, giving you all of these benefits with minimal migration.
+
+Here is an example of how to set up the AI provider:
+
+```ts fileName="intlayer.config.ts"
+import { Locales, type IntlayerConfig } from "intlayer";
+import { loadJSON, syncJSON } from "@intlayer/sync-json-plugin";
+
+const config: IntlayerConfig = {
+  internationalization: {
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
+  },
+  ai: {
+    provider: "openai",
+    model: "gpt-5-mini",
+    apiKey: process.env.OPENAI_API_KEY,
+  },
+  plugins: [
+    syncJSON({
+      source: ({ key, locale }) => `./public/locales/${locale}/${key}.json`,
+    }),
+  ],
+};
+
+export default config;
+```
+
+Then you can execute the following command to fill your translations:
+
+```bash
+npx intlayer fill
+```
+
+This will fill your translations with the AI provider you have configured.
+
+> See all the available AI providers in the [Intlayer AI configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md#ai-configuration).
+> See all the available commands in the [Intlayer CLI documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_cli.md).
+
+---
+
 ## Git Configuration
 
 Exclude generated files from version control:

package/blog/en/intlayer_with_next-intl.md

@@ -1,12 +1,15 @@
 ---
 createdAt: 2025-01-02
-updatedAt: 2025-10-29
+updatedAt: 2025-11-06
 title: How to automate your next-intl JSON translations using Intlayer
 description: Automate your JSON translations with Intlayer and next-intl for enhanced internationalization in Next.js applications.
 slugs:
   - blog
   - intlayer-with-next-intl
 history:
+  - version: 7.0.7
+    date: 2025-11-06
+    changes: Add AI provider support doc
   - version: 7.0.6
     date: 2025-11-01
     changes: Add loadJSON plugin
@@ -25,16 +28,23 @@ See a concrete comparison with next-intl in our [next-i18next vs. next-intl vs.
 
 ## Why Combine Intlayer with next-intl?
 
-While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with next-intl for several reasons:
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-1. **Existing codebase**: You have an established next-intl implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing next-intl plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with next-intl but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-**For that, Intlayer can be implemented as an adapter for next-intl to help automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+However, **next-intl** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with next-intl.
+By combining **Intlayer** with **next-intl**, you get the best of both worlds — next-intl’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for next-intl**, allowing you to:
+
+- Gradually migrate from next-intl to Intlayer.
+- Keep existing next-intl plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 
@@ -144,6 +154,59 @@ export default config;
 
 This will load all the JSON files in the `src` directory that match the pattern `{key}.i18n.json` and load them as Intlayer dictionaries.
 
+---
+
+### Step 4: Set up AI provider
+
+Intlayer unlocks a set of advanced automation and developer-friendly features for your i18next workflow.
+
+- **Automatic detection and filling of missing translations**: Intlayer scans your JSON dictionaries, finds untranslated or missing keys, and translates only those, so 99% of your JSON remains untouched.
+- **Chunked translation for large JSON files**: When your translation files are very large, Intlayer automatically splits processing into manageable chunks, translating them independently to avoid API limits and memory issues.
+- **Namespace parallelization**: If you have hundreds of namespaces (or files), Intlayer parallelizes the translation tasks, efficiently speeding up your CI/CD or bulk translation operations.
+- **Flexible AI provider support**: Choose your preferred AI provider (e.g., OpenAI, Claude, Gemini), simply by configuring credentials. Use your own API key, and switch providers as needed.
+- **Resilient AI response handling**: Intlayer can handle edge cases where your AI provider returns text as either a string or an object, even auto-retrying when the format is inconsistent.
+- **CLI & CI/CD ready**: Run Intlayer’s checks and auto-filling directly in your tests or pipelines, making your localization process robust and automated.
+- **Integrates on top of your existing setup**: You don’t need to change your i18next or Next.js foundation. Intlayer works as an add-on plugin to your current setup, giving you all of these benefits with minimal migration.
+
+Here is an example of how to set up the AI provider:
+
+```ts fileName="intlayer.config.ts"
+import { Locales, type IntlayerConfig } from "intlayer";
+import { loadJSON, syncJSON } from "@intlayer/sync-json-plugin";
+
+const config: IntlayerConfig = {
+  internationalization: {
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
+  },
+  ai: {
+    provider: "openai",
+    model: "gpt-5-mini",
+    apiKey: process.env.OPENAI_API_KEY,
+  },
+  plugins: [
+    syncJSON({
+      source: ({ key, locale }) => `./messages/${locale}/${key}.json`,
+    }),
+  ],
+};
+
+export default config;
+```
+
+Then you can execute the following command to fill your translations:
+
+```bash
+npx intlayer fill
+```
+
+This will fill your translations with the AI provider you have configured.
+
+> See all the available AI providers in the [Intlayer AI configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md#ai-configuration).
+> See all the available commands in the [Intlayer CLI documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_cli.md).
+
+---
+
 ## Git Configuration
 
 It's recommended to ignore auto-generated Intlayer files:

package/blog/en/intlayer_with_react-i18next.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-01-02
-updatedAt: 2025-10-29
+updatedAt: 2025-11-06
 title: How to automate your react-i18next JSON translations using Intlayer
 description: Automate your JSON translations with Intlayer and react-i18next for enhanced internationalization in React applications.
 keywords:
@@ -18,6 +18,9 @@ slugs:
   - blog
   - intlayer-with-react-i18next
 history:
+  - version: 7.0.7
+    date: 2025-11-06
+    changes: Add AI provider support doc
   - version: 7.0.6
     date: 2025-11-01
     changes: Add loadJSON plugin
@@ -36,16 +39,25 @@ See a concrete comparison with react-i18next in our [react-i18next vs. react-int
 
 ## Why Combine Intlayer with react-i18next?
 
-While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)), you might want to combine it with react-i18next for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)), you might want to combine it with react-i18next for several reasons.
 
-1. **Existing codebase**: You have an established react-i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing react-i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with react-i18next but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for react-i18next to help automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with react-i18next.
+However, **i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **i18next**, you get the best of both worlds — i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for i18next**, allowing you to:
+
+- Gradually migrate from i18next to Intlayer.
+- Keep existing i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 
@@ -155,6 +167,55 @@ export default config;
 
 This will load all the JSON files in the `src` directory that match the pattern `{key}.i18n.json` and load them as Intlayer dictionaries.
 
+### Step 4: Set up AI provider
+
+Intlayer unlocks a set of advanced automation and developer-friendly features for your i18next workflow.
+
+- **Automatic detection and filling of missing translations**: Intlayer scans your JSON dictionaries, finds untranslated or missing keys, and translates only those, so 99% of your JSON remains untouched.
+- **Chunked translation for large JSON files**: When your translation files are very large, Intlayer automatically splits processing into manageable chunks, translating them independently to avoid API limits and memory issues.
+- **Namespace parallelization**: If you have hundreds of namespaces (or files), Intlayer parallelizes the translation tasks, efficiently speeding up your CI/CD or bulk translation operations.
+- **Flexible AI provider support**: Choose your preferred AI provider (e.g., OpenAI, Claude, Gemini), simply by configuring credentials. Use your own API key, and switch providers as needed.
+- **Resilient AI response handling**: Intlayer can handle edge cases where your AI provider returns text as either a string or an object, even auto-retrying when the format is inconsistent.
+- **CLI & CI/CD ready**: Run Intlayer’s checks and auto-filling directly in your tests or pipelines, making your localization process robust and automated.
+- **Integrates on top of your existing setup**: You don’t need to change your i18next or Next.js foundation. Intlayer works as an add-on plugin to your current setup, giving you all of these benefits with minimal migration.
+
+Here is an example of how to set up the AI provider:
+
+```ts fileName="intlayer.config.ts"
+import { Locales, type IntlayerConfig } from "intlayer";
+import { loadJSON, syncJSON } from "@intlayer/sync-json-plugin";
+
+const config: IntlayerConfig = {
+  internationalization: {
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
+  },
+  ai: {
+    provider: "openai",
+    model: "gpt-5-mini",
+    apiKey: process.env.OPENAI_API_KEY,
+  },
+  plugins: [
+    syncJSON({
+      source: ({ key, locale }) => `./locales/${locale}/${key}.json`,
+    }),
+  ],
+};
+
+export default config;
+```
+
+Then you can execute the following command to fill your translations:
+
+```bash
+npx intlayer fill
+```
+
+This will fill your translations with the AI provider you have configured.
+
+> See all the available AI providers in the [Intlayer AI configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md#ai-configuration).
+> See all the available commands in the [Intlayer CLI documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_cli.md).
+
 ## Git Configuration
 
 It's recommended to ignore auto-generated Intlayer files:

package/blog/en/intlayer_with_react-intl.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-01-02
-updatedAt: 2025-10-29
+updatedAt: 2025-11-06
 title: How to automate your react-intl JSON translations using Intlayer
 description: Automate your JSON translations with Intlayer and react-intl for enhanced internationalization in React applications.
 keywords:
@@ -16,6 +16,9 @@ slugs:
   - blog
   - intlayer-with-react-intl
 history:
+  - version: 7.0.7
+    date: 2025-11-06
+    changes: Add AI provider support doc
   - version: 7.0.6
     date: 2025-11-01
     changes: Add loadJSON plugin
@@ -40,18 +43,23 @@ See a concrete comparison with react-intl in our [react-i18next vs. react-intl v
 
 While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)), you might want to combine it with react-intl for several reasons:
 
-1. **Existing codebase**: You have an established react-intl implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing react-intl plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with react-intl but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you.
 
-**For that, Intlayer can be implemented as an adapter for react-intl to help automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with react-intl.
+However, **react-intl** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
 
-## Table of Contents
+By combining **Intlayer** with **react-intl**, you get the best of both worlds — react-intl’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
 
-<TOC/>
+This guide explains how to leverage Intlayer as an **adapter for react-intl**, allowing you to:
+
+- Gradually migrate from react-intl to Intlayer.
+- Keep existing react-intl plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Step-by-Step Guide to Set Up Intlayer with react-intl
 
@@ -157,6 +165,57 @@ export default config;
 
 This will load all the JSON files in the `src` directory that match the pattern `{key}.i18n.json` and load them as Intlayer dictionaries.
 
+### Step 4: Set up AI provider
+
+Intlayer unlocks a set of advanced automation and developer-friendly features for your i18next workflow.
+
+- **Automatic detection and filling of missing translations**: Intlayer scans your JSON dictionaries, finds untranslated or missing keys, and translates only those, so 99% of your JSON remains untouched.
+- **Chunked translation for large JSON files**: When your translation files are very large, Intlayer automatically splits processing into manageable chunks, translating them independently to avoid API limits and memory issues.
+- **Namespace parallelization**: If you have hundreds of namespaces (or files), Intlayer parallelizes the translation tasks, efficiently speeding up your CI/CD or bulk translation operations.
+- **Flexible AI provider support**: Choose your preferred AI provider (e.g., OpenAI, Claude, Gemini), simply by configuring credentials. Use your own API key, and switch providers as needed.
+- **Resilient AI response handling**: Intlayer can handle edge cases where your AI provider returns text as either a string or an object, even auto-retrying when the format is inconsistent.
+- **CLI & CI/CD ready**: Run Intlayer’s checks and auto-filling directly in your tests or pipelines, making your localization process robust and automated.
+- **Integrates on top of your existing setup**: You don’t need to change your i18next or Next.js foundation. Intlayer works as an add-on plugin to your current setup, giving you all of these benefits with minimal migration.
+
+Here is an example of how to set up the AI provider:
+
+```ts fileName="intlayer.config.ts"
+import { Locales, type IntlayerConfig } from "intlayer";
+import { loadJSON, syncJSON } from "@intlayer/sync-json-plugin";
+
+const config: IntlayerConfig = {
+  internationalization: {
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
+  },
+  ai: {
+    provider: "openai",
+    model: "gpt-5-mini",
+    apiKey: process.env.OPENAI_API_KEY,
+  },
+  plugins: [
+    syncJSON({
+      source: ({ key, locale }) => `./messages/${locale}/${key}.json`,
+    }),
+  ],
+};
+
+export default config;
+```
+
+Then you can execute the following command to fill your translations:
+
+```bash
+npx intlayer fill
+```
+
+This will fill your translations with the AI provider you have configured.
+
+> See all the available AI providers in the [Intlayer AI configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md#ai-configuration).
+> See all the available commands in the [Intlayer CLI documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_cli.md).
+
+---
+
 ## Git Configuration
 
 It's recommended to ignore auto-generated Intlayer files: