@intlayer/docs 8.11.1 → 8.11.3

package/docs/en/intlayer_with_react_router_v7_fs_routes.md

@@ -1,8 +1,8 @@
 ---
 createdAt: 2025-12-07
-updatedAt: 2026-05-06
-title: React Router v7 i18n - How to translate an React Router v7 app in 2026
-description: Learn how to add internationalization (i18n) to your React Router v7 application using Intlayer with file-system based routing. Follow this comprehensive guide to make your app multilingual with locale-aware routing.
+updatedAt: 2026-05-31
+title: React Router v7 i18n - Complete guide with file-system routing
+description: Best solution for bundle size, SEO, performances & maintainability. Make your React Router v7 app multilingual in 2026, LLM translation, Agent Skills & MCP.
 keywords:
   - Internationalization
   - Documentation
@@ -47,17 +47,47 @@ For client-side routing, refer to the [Intlayer with React Router v7](https://gi
 
 <TOC/>
 
-## What is Intlayer?
+## Why Intlayer over alternatives?
 
-**Intlayer** is an innovative, open-source internationalization (i18n) library designed to simplify multilingual support in modern web applications.
+Compared to main solutions like `react-i18next` or `i18next`, Intlayer is a solution that comes with integrated optimizations such as:
 
-With Intlayer, you can:
+<AccordionGroup>
+<Accordion header="Full React Router coverage">
 
-- **Easily manage translations** using declarative dictionaries at the component level.
-- **Dynamically localize metadata**, routes, and content.
-- **Ensure TypeScript support** with autogenerated types, improving autocompletion and error detection.
-- **Benefit from advanced features**, like dynamic locale detection and switching.
-- **Enable locale-aware routing** with React Router v7's file-system based routing system.
+Intlayer is optimized to work perfectly with React Router by offering **locale-aware routing**, **middleware for locale detection**, and all the features needed for scaling internationalization (i18n).
+
+</Accordion>
+<Accordion header="Bundle size">
+
+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.
+
+</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/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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/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 optimizes your content loading at build time.
+
+</Accordion>
+<Accordion header="Scaling with none-dev">
+
+More than just an i18n solution, Intlayer provides an **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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.
+
+</Accordion>
+</AccordionGroup>
 
 ---
 
@@ -95,7 +125,9 @@ With Intlayer, you can:
 
 See [Application Template](https://github.com/aymericzip/intlayer-react-router-v7-fs-routes-template) on GitHub.
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages using your preferred package manager:
 
@@ -132,7 +164,9 @@ bun x intlayer init
 - **@react-router/fs-routes**
   The package that enables file-system based routing for React Router v7.
 
-### Step 2: Configuration of your project
+</Step>
+
+<Step number={2} title="Configuration of your project">
 
 Create a config file to configure the languages of your application:
 
@@ -151,7 +185,9 @@ export default config;
 
 > Through this configuration file, you can set up localized URLs, middleware redirection, cookie names, the location and extension of your content declarations, disable Intlayer logs in the console, and more. For a complete list of available parameters, refer to the [configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).
 
-### Step 3: Integrate Intlayer in Your Vite Configuration
+</Step>
+
+<Step number={3} title="Integrate Intlayer in Your Vite Configuration">
 
 Add the intlayer plugin into your configuration:
 
@@ -167,7 +203,9 @@ export default defineConfig({
 
 > The `intlayer()` Vite plugin is used to integrate Intlayer with Vite. It ensures the building of content declaration files and monitors them in development mode. It defines Intlayer environment variables within the Vite application. Additionally, it provides aliases to optimize performance.
 
-### Step 4: Configure React Router v7 File-System Routes
+</Step>
+
+<Step number={4} title="Configure React Router v7 File-System Routes">
 
 Set up your routing configuration to use file-system based routes with `flatRoutes`:
 
@@ -188,7 +226,9 @@ export default routes;
 
 > The `flatRoutes` function from `@react-router/fs-routes` enables file-system based routing, where the file structure in the `routes/` directory determines your application's routes. The `ignoredRouteFiles` option ensures that Intlayer content declaration files (`.content.ts`, etc.) are not treated as route files.
 
-### Step 5: Create Route Files with File-System Conventions
+</Step>
+
+<Step number={5} title="Create Route Files with File-System Conventions">
 
 With file-system routing, you use a flat naming convention where dots (`.`) represent path segments and parentheses `()` denote optional segments.
 
@@ -355,7 +395,9 @@ export default function AboutPage() {
 }
 ```
 
-### Step 6: Declare Your Content
+</Step>
+
+<Step number={6} title="Declare Your Content">
 
 Create and manage your content declarations to store translations. Place content files alongside your route files:
 
@@ -419,7 +461,9 @@ export default aboutContent;
 
 > If your app already exists, you can use the [Intlayer Compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md), as well as the [extract command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/extract.md), to transform thousands of components in a second.
 
-### Step 7: Create Locale-Aware Components
+</Step>
+
+<Step number={7} title="Create Locale-Aware Components">
 
 Create a `LocalizedLink` component for locale-aware navigation:
 
@@ -480,7 +524,9 @@ export const useLocalizedNavigate = () => {
 };
 ```
 
-### Step 8: Create a Locale Switcher Component
+</Step>
+
+<Step number={8} title="Create a Locale Switcher Component">
 
 Create a component to allow users to change languages:
 
@@ -541,7 +587,9 @@ export const LocaleSwitcher: FC = () => {
 
 > To Learn more about the `useLocale` hook, refer to the [documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/react-intlayer/useLocale.md).
 
-### Step 9: Add HTML Attributes Management (Optional)
+</Step>
+
+<Step number={9} title="Add HTML Attributes Management">
 
 Create a hook to manage HTML lang and dir attributes:
 
@@ -562,7 +610,9 @@ export const useI18nHTMLAttributes = () => {
 
 This hook is already used in the layout component (`($locale)._layout.tsx`) shown in Step 5.
 
-### Step 10: Add middleware (Optional)
+</Step>
+
+<Step number={10} title="Add middleware">
 
 You can also use the `intlayerProxy` 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.
 
@@ -583,7 +633,9 @@ export default defineConfig({
 });
 ```
 
-### (Optional) Step 11: Extract the content of your components
+</Step>
+
+<Step number={11} title="Extract the content of your components" isOptional={true}>
 
 If you have an existing codebase, transforming thousands of files can be time-consuming.
 
@@ -685,6 +737,10 @@ bun run build # Or bun run dev
 
 ---
 
+</Step>
+
+</Steps>
+
 ## Configure TypeScript
 
 Intlayer uses module augmentation to get benefits of TypeScript and make your codebase stronger.

package/docs/en/intlayer_with_storybook.md

@@ -31,16 +31,47 @@ history:
 
 <TOC/>
 
-## What is Intlayer?
+## Why Intlayer over alternatives?
 
-**Intlayer** is an innovative, open-source internationalization (i18n) library designed to simplify multilingual support in modern web applications. It works at the **component level** - each component owns its content declarations - keeping translations co-located with the code that uses them.
+Compared to main solutions like `storybook-react-i18next` or `i18next`, Intlayer is a solution that comes with integrated optimizations such as:
 
-With Intlayer you can:
+<AccordionGroup>
+<Accordion header="Full Storybook coverage">
 
-- **Manage translations declaratively** with per-component content files.
-- **Get full TypeScript support** through auto-generated types and IDE autocompletion.
-- **Switch locales at runtime** without a page reload.
-- **Translate automatically** with built-in AI provider integrations.
+Intlayer is optimized to work perfectly with Storybook by offering **multilingual story decorators**, **locale switching**, and all the features needed for scaling internationalization (i18n) across your design system.
+
+</Accordion>
+<Accordion header="Bundle size">
+
+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.
+
+</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/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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/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 optimizes your content loading at build time.
+
+</Accordion>
+<Accordion header="Scaling with none-dev">
+
+More than just an i18n solution, Intlayer provides an **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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.
+
+</Accordion>
+</AccordionGroup>
 
 ---
 
@@ -59,7 +90,9 @@ Storybook is the industry-standard tool for developing and documenting UI compon
 <Tabs>
 <Tab value="Vite Setup">
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 ```bash packageManager="npm"
 npm install intlayer react-intlayer
@@ -89,7 +122,9 @@ bun add vite-intlayer --dev
 
 ---
 
-### Step 2: Create an Intlayer Configuration
+</Step>
+
+<Step number={2} title="Create an Intlayer Configuration">
 
 Create `intlayer.config.ts` at the root of your project (or inside your design-system package):
 
@@ -118,7 +153,9 @@ export default config;
 
 ---
 
-### Step 3: Add the Vite Plugin to Storybook
+</Step>
+
+<Step number={3} title="Add the Vite Plugin to Storybook">
 
 Storybook's `viteFinal` hook lets you extend the internal Vite config. Import and add the `intlayer()` plugin there:
 
@@ -159,7 +196,9 @@ The `intlayer()` plugin watches your `*.content.ts` files and rebuilds dictionar
 
 ---
 
-### Step 4: Add the `IntlayerProvider` Decorator and a Locale Toolbar
+</Step>
+
+<Step number={4} title="Add the `IntlayerProvider` Decorator and a Locale Toolbar">
 
 Storybook's `preview` file is the right place to wrap every story with the `IntlayerProvider` and expose a locale switcher in the toolbar:
 
@@ -216,7 +255,9 @@ export default preview;
 </Tab>
 <Tab value="Webpack Setup">
 
-### Step 1: Install Dependencies
+</Step>
+
+<Step number={1} title="Install Dependencies">
 
 ```bash packageManager="npm"
 npm install intlayer react-intlayer
@@ -240,7 +281,9 @@ bun add @intlayer/webpack --dev
 
 ---
 
-### Step 2: Create an Intlayer Configuration
+</Step>
+
+<Step number={2} title="Create an Intlayer Configuration">
 
 Create `intlayer.config.ts` at the root of your project:
 
@@ -262,7 +305,9 @@ export default config;
 
 ---
 
-### Step 3: Configure Storybook's Webpack
+</Step>
+
+<Step number={3} title="Configure Storybook's Webpack">
 
 For Webpack-based Storybook setups (e.g. `@storybook/react-webpack5`), extend the webpack config via `webpackFinal` to add the Intlayer aliases and loader:
 
@@ -289,7 +334,9 @@ export default config;
 
 ---
 
-### Step 4: Add the `IntlayerProvider` Decorator and a Locale Toolbar
+</Step>
+
+<Step number={4} title="Add the `IntlayerProvider` Decorator and a Locale Toolbar">
 
 Same as the Vite setup - add the decorator and global locale type in `.storybook/preview.tsx`:
 
@@ -335,6 +382,10 @@ export default preview;
 
 ---
 
+</Step>
+
+</Steps>
+
 ## Declaring Content
 
 Create a `*.content.ts` file next to each component. Intlayer picks it up automatically during compilation.

package/docs/en/intlayer_with_svelte_kit.md

@@ -1,8 +1,8 @@
 ---
 createdAt: 2025-11-20
-updatedAt: 2026-05-06
-title: SvelteKit i18n - How to translate an SvelteKit app in 2026
-description: Discover how to make your SvelteKit website multilingual. Follow the documentation to internationalize (i18n) and translate it using Server-Side Rendering (SSR).
+updatedAt: 2026-05-31
+title: SvelteKit i18n - Complete guide to translate a SvelteKit app
+description: Best solution for bundle size, SEO, performances & maintainability. Make your SvelteKit website multilingual in 2026, LLM translation, Agent Skills & MCP.
 keywords:
   - Internationalization
   - Documentation
@@ -59,16 +59,47 @@ history:
 
 <TOC/>
 
-## What is Intlayer?
+## Why Intlayer over alternatives?
 
-**Intlayer** is an innovative, open-source internationalization (i18n) library designed to simplify multilingual support in modern web applications. It works seamlessly with **SvelteKit's** Server-Side Rendering (SSR) capabilities.
+Compared to main solutions like `svelte-i18n` or `i18next`, Intlayer is a solution that comes with integrated optimizations such as:
 
-With Intlayer, you can:
+<AccordionGroup>
+<Accordion header="Full SvelteKit coverage">
 
-- **Easily manage translations** using declarative dictionaries at the component level.
-- **Dynamically localize metadata**, routes, and content.
-- **Ensure TypeScript support** with autogenerated types.
-- **Leverage SvelteKit's SSR** for SEO-friendly internationalization.
+Intlayer is optimized to work perfectly with SvelteKit by offering **multilingual routing**, **SSR support**, and all the features needed for scaling internationalization (i18n).
+
+</Accordion>
+<Accordion header="Bundle size">
+
+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.
+
+</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/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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/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 optimizes your content loading at build time.
+
+</Accordion>
+<Accordion header="Scaling with none-dev">
+
+More than just an i18n solution, Intlayer provides an **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/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.
+
+</Accordion>
+</AccordionGroup>
 
 ---
 
@@ -118,7 +149,9 @@ To get started, create a new SvelteKit project. Here is the final structure that
 └── vite.config.ts
 ```
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages using npm:
 
@@ -150,7 +183,9 @@ bun x intlayer init
 - **svelte-intlayer**: Provides context providers and stores for Svelte/SvelteKit.
 - **vite-intlayer**: The Vite plugin to integrate content declarations with the build process.
 
-### Step 2: Configuration of your project
+</Step>
+
+<Step number={2} title="Configuration of your project">
 
 Create a config file in your project root:
 
@@ -167,7 +202,9 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-### Step 3: Integrate Intlayer in Your Vite Configuration
+</Step>
+
+<Step number={3} title="Integrate Intlayer in Your Vite Configuration">
 
 Update your `vite.config.ts` to include the Intlayer plugin. This plugin handles the transpilation of your content files.
 
@@ -181,7 +218,9 @@ export default defineConfig({
 });
 ```
 
-### Step 4: Declare Your Content
+</Step>
+
+<Step number={4} title="Declare Your Content">
 
 Create your content declaration files anywhere in your `src` folder (e.g., `src/lib/content` or alongside your components). These files define the translatable content for your application using the `t()` function for each locale.
 
@@ -202,7 +241,9 @@ const heroContent = {
 export default heroContent;
 ```
 
-### Step 5: Utilize Intlayer in Your Components
+</Step>
+
+<Step number={5} title="Utilize Intlayer in Your Components">
 
 Now you can use the `useIntlayer` function in any Svelte component. It returns a reactive store that automatically updates when the locale changes. The function will automatically respect the current locale (both during SSR and client-side navigation).
 
@@ -226,7 +267,9 @@ Now you can use the `useIntlayer` function in any Svelte component. It returns a
 <div aria-label={String($content.title)}></div>
 ```
 
-### (Optional) Step 6: Set up routing
+</Step>
+
+<Step number={6} title="Set up routing" isOptional={true}>
 
 The following steps show how to set up locale-based routing in SvelteKit. This allows your URLs to include the locale prefix (e.g., `/en/about`, `/fr/about`) for better SEO and user experience.
 
@@ -251,7 +294,9 @@ The following steps show how to set up locale-based routing in SvelteKit. This a
         └── +layout.svelte         # Root layout for fonts and global styles
 ```
 
-### Step 7: Handle Server-Side Locale Detection (Hooks)
+</Step>
+
+<Step number={7} title="Handle Server-Side Locale Detection">
 
 In SvelteKit, the server needs to know the user's locale to render the correct content during SSR. We use `hooks.server.ts` to detect the locale from the URL or cookies.
 
@@ -463,7 +508,9 @@ export const prerender = true;
 </style>
 ```
 
-### (Optional) Step 8: Internationalized Links
+</Step>
+
+<Step number={8} title="Internationalized Links" isOptional={true}>
 
 For SEO, it is recommended to prefix your routes with the locale (e.g., `/en/about`, `/fr/about`). This component automatically prefixes any link with the current locale.
 
@@ -496,7 +543,9 @@ const localizedPath = getLocalizedUrl("/about", $locale);
 goto(localizedPath); // Navigates to /en/about or /fr/about depending on locale
 ```
 
-### (Optional) Step 9: Language Switcher
+</Step>
+
+<Step number={9} title="Language Switcher" isOptional={true}>
 
 To allow users to switch languages, update the URL.
 
@@ -537,7 +586,9 @@ To allow users to switch languages, update the URL.
 </style>
 ```
 
-### (Optional) Step 10: Add backend proxy
+</Step>
+
+<Step number={10} title="Add backend proxy" isOptional={true}>
 
 To add a backend proxy to your SvelteKit application, you can use the `intlayerProxy` function provided by the `vite-intlayer` plugin. This plugin will automatically detect the best locale for the user based on the URL, cookies, and browser language preferences.
 
@@ -556,7 +607,9 @@ export default defineConfig({
 });
 ```
 
-### (Optional) Step 11: Set up the intlayer editor / CMS
+</Step>
+
+<Step number={11} title="Set up the intlayer editor / CMS" isOptional={true}>
 
 To set up the intlayer editor, you must follow the [intlayer editor documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md).
 
@@ -581,7 +634,9 @@ To be able to visualize the intlayer editor selector, you will have to use the c
 </div>
 ```
 
-### (Optional) Step 12: Extract the content of your components
+</Step>
+
+<Step number={12} title="Extract the content of your components" isOptional={true}>
 
 If you have an existing codebase, transforming thousands of files can be time-consuming.
 
@@ -696,3 +751,7 @@ It is recommended to ignore the files generated by Intlayer.
 
 - **Visual Editor**: Integrate the [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md) to edit translations directly from the UI.
 - **CMS**: Externalize your content management using the [Intlayer CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md).
+
+</Step>
+
+</Steps>