@intlayer/docs 6.1.4 → 6.1.6-canary.0

package/blog/en/next-i18next_vs_next-intl_vs_intlayer.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-09-25
+updatedAt: 2025-09-29
 title: next-i18next vs next-intl vs Intlayer
 description: Compare next-i18next with next-intl and Intlayer for the internationalization (i18n) of a Next.js app
 keywords:
@@ -19,6 +19,8 @@ slugs:
 
 # next-i18next VS next-intl VS intlayer | Next.js Internationalization (i18n)
 
+![next-i18next VS next-intl VS intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/assets/i18next-next-intl-intlayer.png?raw=true)
+
 Let’s take a look into the similarities and differences between three i18n options for Next.js: next-i18next, next-intl, and Intlayer.
 
 This is not a full tutorial. It’s a comparison to help you pick.
@@ -47,12 +49,12 @@ We focus on **Next.js 13+ App Router** (with **React Server Components**) and ev
 
 ---
 
-| Library                | GitHub Stars                                                                                                                                                            | Total Commits                                                                                                                                                               | Last Commit                                                                                                                                  | First Version | NPM Version                                                                                                | NPM Downloads                                                                                                         |
-| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `aymericzip/intlayer`  | [![GitHub Repo stars](https://img.shields.io/github/stars/aymericzip/intlayer?style=flat&label=%E2%AD%90%20stars)](https://github.com/aymericzip/intlayer/stargazers)   | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/aymericzip/intlayer?style=flat&label=commits)](https://github.com/aymericzip/intlayer/commits)   | [![Last Commit](https://img.shields.io/github/last-commit/aymericzip/intlayer?style=flat)](https://github.com/aymericzip/intlayer/commits)   | April 2024    | [![npm](https://img.shields.io/npm/v/intlayer?style=flat)](https://www.npmjs.com/package/intlayer)         | [![npm downloads](https://img.shields.io/npm/dm/intlayer?style=flat)](https://www.npmjs.com/package/intlayer)         |
-| `amannn/next-intl`     | [![GitHub Repo stars](https://img.shields.io/github/stars/amannn/next-intl?style=flat&label=%E2%AD%90%20stars)](https://github.com/amannn/next-intl/stargazers)         | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/amannn/next-intl?style=flat&label=commits)](https://github.com/amannn/next-intl/commits)         | [![Last Commit](https://img.shields.io/github/last-commit/amannn/next-intl?style=flat)](https://github.com/amannn/next-intl/commits)         | Nov 2020      | [![npm](https://img.shields.io/npm/v/next-intl?style=flat)](https://www.npmjs.com/package/next-intl)       | [![npm downloads](https://img.shields.io/npm/dm/next-intl?style=flat)](https://www.npmjs.com/package/next-intl)       |
-| `i18next/i18next`      | [![GitHub Repo stars](https://img.shields.io/github/stars/i18next/i18next?style=flat&label=%E2%AD%90%20stars)](https://github.com/i18next/i18next/stargazers)           | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/i18next/i18next?style=flat&label=commits)](https://github.com/i18next/i18next/commits)           | [![Last Commit](https://img.shields.io/github/last-commit/i18next/i18next?style=flat)](https://github.com/i18next/i18next/commits)           | Jan 2012      | [![npm](https://img.shields.io/npm/v/i18next?style=flat)](https://www.npmjs.com/package/i18next)           | [![npm downloads](https://img.shields.io/npm/dm/i18next?style=flat)](https://www.npmjs.com/package/i18next)           |
-| `i18next/next-i18next` | [![GitHub Repo stars](https://img.shields.io/github/stars/i18next/next-i18next?style=flat&label=%E2%AD%90%20stars)](https://github.com/i18next/next-i18next/stargazers) | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/i18next/next-i18next?style=flat&label=commits)](https://github.com/i18next/next-i18next/commits) | [![Last Commit](https://img.shields.io/github/last-commit/i18next/next-i18next?style=flat)](https://github.com/i18next/next-i18next/commits) | Nov 2018      | [![npm](https://img.shields.io/npm/v/next-i18next?style=flat)](https://www.npmjs.com/package/next-i18next) | [![npm downloads](https://img.shields.io/npm/dm/next-i18next?style=flat)](https://www.npmjs.com/package/next-i18next) |
+| Library                | GitHub Stars                                                                                                                                                                     | Total Commits                                                                                                                                                                        | Last Commit                                                                                                                                           | First Version | NPM Version                                                                                                         | NPM Downloads                                                                                                                  |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| `aymericzip/intlayer`  | [![GitHub Repo stars](https://img.shields.io/github/stars/aymericzip/intlayer?style=for-the-badge&label=%E2%AD%90%20stars)](https://github.com/aymericzip/intlayer/stargazers)   | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/aymericzip/intlayer?style=for-the-badge&label=commits)](https://github.com/aymericzip/intlayer/commits)   | [![Last Commit](https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge)](https://github.com/aymericzip/intlayer/commits)   | April 2024    | [![npm](https://img.shields.io/npm/v/intlayer?style=for-the-badge)](https://www.npmjs.com/package/intlayer)         | [![npm downloads](https://img.shields.io/npm/dm/intlayer?style=for-the-badge)](https://www.npmjs.com/package/intlayer)         |
+| `amannn/next-intl`     | [![GitHub Repo stars](https://img.shields.io/github/stars/amannn/next-intl?style=for-the-badge&label=%E2%AD%90%20stars)](https://github.com/amannn/next-intl/stargazers)         | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/amannn/next-intl?style=for-the-badge&label=commits)](https://github.com/amannn/next-intl/commits)         | [![Last Commit](https://img.shields.io/github/last-commit/amannn/next-intl?style=for-the-badge)](https://github.com/amannn/next-intl/commits)         | Nov 2020      | [![npm](https://img.shields.io/npm/v/next-intl?style=for-the-badge)](https://www.npmjs.com/package/next-intl)       | [![npm downloads](https://img.shields.io/npm/dm/next-intl?style=for-the-badge)](https://www.npmjs.com/package/next-intl)       |
+| `i18next/i18next`      | [![GitHub Repo stars](https://img.shields.io/github/stars/i18next/i18next?style=for-the-badge&label=%E2%AD%90%20stars)](https://github.com/i18next/i18next/stargazers)           | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/i18next/i18next?style=for-the-badge&label=commits)](https://github.com/i18next/i18next/commits)           | [![Last Commit](https://img.shields.io/github/last-commit/i18next/i18next?style=for-the-badge)](https://github.com/i18next/i18next/commits)           | Jan 2012      | [![npm](https://img.shields.io/npm/v/i18next?style=for-the-badge)](https://www.npmjs.com/package/i18next)           | [![npm downloads](https://img.shields.io/npm/dm/i18next?style=for-the-badge)](https://www.npmjs.com/package/i18next)           |
+| `i18next/next-i18next` | [![GitHub Repo stars](https://img.shields.io/github/stars/i18next/next-i18next?style=for-the-badge&label=%E2%AD%90%20stars)](https://github.com/i18next/next-i18next/stargazers) | [![GitHub commit activity](https://img.shields.io/github/commit-activity/t/i18next/next-i18next?style=for-the-badge&label=commits)](https://github.com/i18next/next-i18next/commits) | [![Last Commit](https://img.shields.io/github/last-commit/i18next/next-i18next?style=for-the-badge)](https://github.com/i18next/next-i18next/commits) | Nov 2018      | [![npm](https://img.shields.io/npm/v/next-i18next?style=for-the-badge)](https://www.npmjs.com/package/next-i18next) | [![npm downloads](https://img.shields.io/npm/dm/next-i18next?style=for-the-badge)](https://www.npmjs.com/package/next-i18next) |
 
 > Badges update automatically. Snapshots will vary over time.
 
@@ -140,6 +142,7 @@ Two important issues:
   > If I'm on the `/about` page, I don't want to load the content of the `/home` page
 
 - **Splitting by locale:**
+
   > If I'm on the `/fr/about` page, I don't want to load the content of the `/en/about` page
 
 Again, all three solutions are aware of these issues and allow managing these optimizations. The difference between the three solutions is the DX (Developer Experience).
@@ -162,14 +165,183 @@ How the library handles fallbacks is also important. Let's consider that the app
 
 In the case of `next-intl` and `next-i18next`, the library requires loading the JSON related to the current locale, but also to the fallback locale. Thus, considering that all content has been translated, each page will load 100% unnecessary content. **In comparison, `intlayer` processes the fallback at dictionary build time. Thus, each page will load only the content used.**
 
+> Note: To optimize the bundle using `intlayer`, you need to set the `importMode: 'dynamic'` option in your `intlayer.config.ts` file. And ensure the plugin `@intlayer/babel` / `@intlayer/swc` is installed (installed by default using `vite-intlayer`).
+
 Here an example of the impact of bundle size optimization using `intlayer` in a vite + react application:
 
-| Optimized bundle                                                                             | Bundle not optimized                                                                                            |
-| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
-| ![optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle.png) | ![no optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle_no_optimization.png) |
+| Optimized bundle                                                                                      | Bundle not optimized                                                                                                     |
+| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| ![optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle.png?raw=true) | ![no optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle_no_optimization.png?raw=true) |
+
+---
+
+## TypeScript & safety
+
+<Columns>
+  <Column>
+
+**next-intl**
+
+- Solid TypeScript support, but **keys aren’t strictly typed by default**; you’ll maintain safety patterns manually.
+
+  </Column>
+  <Column>
+
+**next-i18next**
+
+- Base typings for hooks; **strict key typing requires extra tooling/config**.
+
+  </Column>
+  <Column>
+
+**intlayer**
+
+- **Generates strict types** from your content. **IDE autocompletion** and **compile-time errors** catch typos and missing keys before deploy.
+
+  </Column>
+</Columns>
+
+**Why it matters:** Strong typing shifts failures **left** (CI/build) instead of **right** (runtime).
+
+---
+
+## Missing translation handling
+
+<Columns>
+  <Column>
+
+**next-intl**
+
+- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+
+  </Column>
+  <Column>
+
+**next-i18next**
+
+- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+
+  </Column>
+  <Column>
+
+**intlayer**
+
+- **Build-time detection** with **warnings/errors** for missing locales or keys.
+
+  </Column>
+</Columns>
+
+**Why it matters:** Catching gaps during build prevents “mystery strings” in production and aligns with strict release gates.
+
+---
+
+## Routing, middleware & URL strategy
+
+<Columns>
+  <Column>
+
+**next-intl**
+
+- Works with **Next.js localized routing** on the App Router.
+
+  </Column>
+  <Column>
+
+**next-i18next**
+
+- Works with **Next.js localized routing** on the App Router.
+
+  </Column>
+  <Column>
+
+**intlayer**
+
+- All of the above, plus **i18n middleware** (locale detection via headers/cookies) and **helpers** to generate localized URLs and `<link rel="alternate" hreflang="…">` tags.
+
+  </Column>
+</Columns>
+
+**Why it matters:** Fewer custom glue layers; **consistent UX** and **clean SEO** across locales.
+
+---
+
+## Server Components (RSC) alignment
+
+<Columns>
+  <Column>
+
+**next-intl**
+
+- Supports Next.js 13+. Often requires passing t-functions/formatters through component trees in hybrid setups.
+
+  </Column>
+  <Column>
+
+**next-i18next**
+
+- Supports Next.js 13+. Similar constraints with passing translation utilities across boundaries.
+
+  </Column>
+  <Column>
+
+**intlayer**
+
+- Supports Next.js 13+ and smooths the **server/client boundary** with a consistent API and RSC-oriented providers, avoiding shuttling formatters or t-functions.
+
+  </Column>
+</Columns>
+
+**Why it matters:** Cleaner mental model and fewer edge cases in hybrid trees.
 
 ---
 
+## DX, tooling & maintenance
+
+<Columns>
+  <Column>
+
+**next-intl**
+
+- Commonly paired with external localization platforms and editorial workflows.
+
+  </Column>
+  <Column>
+
+**next-i18next**
+
+- Commonly paired with external localization platforms and editorial workflows.
+
+  </Column>
+  <Column>
+
+**intlayer**
+
+- Ships a **free Visual Editor** and **optional CMS** (Git-friendly or externalized), plus a **VSCode extension** and **AI-assisted translations** using your own provider keys.
+
+  </Column>
+</Columns>
+
+**Why it matters:** Lowers ops cost and shortens the loop between developers and content authors.
+
+## Integration with localization platforms (TMS)
+
+Large organizations often rely on Translation Management Systems (TMS) like **Crowdin**, **Phrase**, **Lokalise**, **Localizely**, or **Localazy**.
+
+- **Why companies care**
+  - **Collaboration & roles**: Multiple actors are involved: developers, product managers, translators, reviewers, marketing teams.
+  - **Scale & efficiency**: continuous localization, in‑context review.
+
+- **next-intl / next-i18next**
+  - Typically use **centralized JSON catalogs**, so export/import with TMS is straightforward.
+  - Mature ecosystems and examples/integrations for the platforms above.
+
+- **Intlayer**
+  - Encourages **decentralized, per-component dictionaries** and supports **TypeScript/TSX/JS/JSON/MD** content.
+  - This improves modularity in code, but can make plug‑and‑play TMS integration harder when a tool expects centralized, flat JSON files.
+  - Intlayer provides alternatives: **AI‑assisted translations** (using your own provider keys), a **Visual Editor/CMS**, and **CLI/CI** workflows to catch and prefill gaps.
+
+> Note: `next-intl` and `i18next` also accepts TypeScript catalogs. If your team stores messages in `.ts` files or decentralizes them by feature, you can face similar TMS friction. However, many `next-intl` setups remain centralized in a `locales/` folder, which is a bit easier to refactor to JSON for TMS.
+
 ## Developer Experience
 
 This part makes a deep comparison between the three solutions. Rather than considering simple cases, as described in the 'getting started' documentation for each solution, we will consider a real use case, more similar to a real project.
@@ -184,32 +356,33 @@ The app structure is important to ensure good maintainability for your codebase.
 
 ```bash
 .
-├── public
-│   └── locales
-│       ├── en
-│       │  ├── home.json
-│       │  └── navbar.json
-│       ├── fr
-│       │  ├── home.json
-│       │  └── navbar.json
-│       └── es
-│          ├── home.json
-│          └── navbar.json
-├── next-i18next.config.js
+├── i18n.config.ts
 └── src
-    ├── middleware.ts
+    ├── locales
+    │   ├── en
+    │   │  ├── common.json
+    │   │  └── about.json
+    │   └── fr
+    │      ├── common.json
+    │      └── about.json
     ├── app
-    │   └── home.tsx
+    │   ├── i18n
+    │   │   └── server.ts
+    │   └── [locale]
+    │       ├── layout.tsx
+    │       └── about.tsx
     └── components
-        └── Navbar
-            └── index.tsx
+        ├── I18nProvider.tsx
+        ├── ClientComponent.tsx
+        └── ServerComponent.tsx
 ```
 
   </TabItem>
-    <TabItem label="next-intl" value="next-intl">
+  <TabItem label="next-intl" value="next-intl">
 
 ```bash
 .
+├── i18n.ts
 ├── locales
 │   ├── en
 │   │  ├── home.json
@@ -220,11 +393,13 @@ The app structure is important to ensure good maintainability for your codebase.
 │   └── es
 │      ├── home.json
 │      └── navbar.json
-├── i18n.ts
 └── src
     ├── middleware.ts
     ├── app
-    │   └── home.tsx
+    │   ├── i18n
+    │   │   └── server.ts
+    │   └── [locale]
+    │       └── home.tsx
     └── components
         └── Navbar
             └── index.tsx
@@ -239,9 +414,11 @@ The app structure is important to ensure good maintainability for your codebase.
 └── src
     ├── middleware.ts
     ├── app
-    │   └── home
-    │       └── index.tsx
-    │       └── index.content.ts
+    │   └── [locale]
+    │       ├── layout.tsx
+    │       └── home
+    │           ├── index.tsx
+    │           └── index.content.ts
     └── components
         └── Navbar
             ├── index.tsx
@@ -253,194 +430,287 @@ The app structure is important to ensure good maintainability for your codebase.
 
 #### Comparison
 
-##### Configuration
-
-Intlayer uses a centralized configuration file to set up your locale, middleware, build, etc.
+- **next-intl / next-i18next**: Centralized catalogs (JSON; namespaces/messages). Clear structure, integrates well with translation platforms, but can lead to more cross-file edits as apps grow.
+- **Intlayer**: Per-component `.content.{ts|js|json}` dictionaries co-located with components. Easier component reuse and local reasoning; adds files and relies on build-time tooling.
 
-##### Content declaration
-
-The centralized type of architecture slows down the development process and makes the codebase more complex to maintain for several reasons:
+#### Setup and Loading Content
 
-1. **For any new component created, you should:**
-   - Create the new resource/namespace in the `locales` folder
-   - Remember to import the new namespace in your page
-   - Translate your content (often done manually by copy/paste from AI providers)
+As mentioned previously, you must optimize how each JSON file is imported into your code.
+How the library handles content loading is important.
 
-2. **For any change made on your components, you should:**
-   - Search for the related resource/namespace (far from the component)
-   - Translate your content
-   - Ensure your content is up to date for any locale
-   - Verify your namespace doesn't include unused keys/values
-   - Ensure the structure of your JSON files is the same for all locales
+<Tab defaultTab="next-intl" group='techno'>
+  <TabItem label="next-i18next" value="next-i18next">
 
-On professional projects using these solutions, localization platforms are often used to help manage the translation of your content. However, this can quickly become costly for large projects.
+```ts fileName="i18n.config.ts"
+export const locales = ["en", "fr"] as const;
+export type Locale = (typeof locales)[number];
 
-To solve this problem, Intlayer adopts an approach that scopes your content per-component and keeps your content close to your component, as we often do with CSS (`styled-components`), types, documentation (`storybook`), or unit tests (`jest`).
+export const defaultLocale: Locale = "en";
 
-This approach allows you to:
+export const rtlLocales = ["ar", "he", "fa", "ur"] as const;
+export const isRtl = (locale: string) =>
+  (rtlLocales as readonly string[]).includes(locale);
 
-1. **Increase the speed of development**
-   - `.content.{{ts|js|json}}` files can be created using a VSCode extension
-   - Autocompletion AI tools in your IDE (such as GitHub Copilot) can help you declare your content, reducing copy/paste
+export function localizedPath(locale: string, path: string) {
+  return locale === defaultLocale ? path : "/" + locale + path;
+}
 
-2. **Clean your codebase**
-   - Reduce the complexity
-   - Increase the maintainability
+const ORIGIN = "https://example.com";
+export function abs(locale: string, path: string) {
+  return ORIGIN + localizedPath(locale, path);
+}
+```
 
-3. **Duplicate your components and their related content more easily (Example: login/register components, etc.)**
-   - By limiting the risk of impacting other components' content
-   - By copy/pasting your content from one application to another without external dependencies
+```ts fileName="src/app/i18n/server.ts"
+import { createInstance } from "i18next";
+import { initReactI18next } from "react-i18next/initReactI18next";
+import resourcesToBackend from "i18next-resources-to-backend";
+import { defaultLocale } from "@/i18n.config";
+
+// Load JSON resources from src/locales/<locale>/<namespace>.json
+const backend = resourcesToBackend(
+  (locale: string, namespace: string) =>
+    import(`../../locales/${locale}/${namespace}.json`)
+);
+
+export async function initI18next(
+  locale: string,
+  namespaces: string[] = ["common"]
+) {
+  const i18n = createInstance();
+  await i18n
+    .use(initReactI18next)
+    .use(backend)
+    .init({
+      lng: locale,
+      fallbackLng: defaultLocale,
+      ns: namespaces,
+      defaultNS: "common",
+      interpolation: { escapeValue: false },
+      react: { useSuspense: false },
+    });
+  return i18n;
+}
+```
 
-4. **Avoid polluting your codebase with unused keys/values for unused components**
-   - If you don't use a component, Intlayer will not import its related content
-   - If you delete a component, you'll more easily remember to remove its related content as it will be present in the same folder
+```tsx fileName="src/components/I18nProvider.tsx"
+"use client";
 
-5. **Reduce reasoning cost for AI agents to declare your multilingual content**
-   - The AI agent won't have to scan your entire codebase to know where to implement your content
-   - Translations can easily be done by autocompletion AI tools in your IDE (such as GitHub Copilot)
+import * as React from "react";
+import { I18nextProvider } from "react-i18next";
+import { createInstance } from "i18next";
+import { initReactI18next } from "react-i18next/initReactI18next";
+import resourcesToBackend from "i18next-resources-to-backend";
+import { defaultLocale } from "@/i18n.config";
+
+const backend = resourcesToBackend(
+  (locale: string, namespace: string) =>
+    import(`../../locales/${locale}/${namespace}.json`)
+);
+
+type Props = {
+  locale: string;
+  namespaces?: string[];
+  resources?: Record<string, any>; // { ns: bundle }
+  children: React.ReactNode;
+};
 
-6. **Optimize loading performance**
-   - If a component is lazy-loaded, its related content will be loaded at the same time
+export default function I18nProvider({
+  locale,
+  namespaces = ["common"],
+  resources,
+  children,
+}: Props) {
+  const [i18n] = React.useState(() => {
+    const i = createInstance();
+
+    i.use(initReactI18next)
+      .use(backend)
+      .init({
+        lng: locale,
+        fallbackLng: defaultLocale,
+        ns: namespaces,
+        resources: resources ? { [locale]: resources } : undefined,
+        defaultNS: "common",
+        interpolation: { escapeValue: false },
+        react: { useSuspense: false },
+      });
+
+    return i;
+  });
 
-#### Setup and Loading Content
+  return <I18nextProvider i18n={i18n}>{children}</I18nextProvider>;
+}
+```
 
-As mentioned previously, you must optimize how each JSON file is imported into your code.
-How the library handles content loading is important.
+```tsx fileName="src/app/[locale]/layout.tsx"
+import type { ReactNode } from "react";
+import { locales, defaultLocale, isRtl, type Locale } from "@/i18n.config";
 
-<Tab defaultTab="next-intl" group='techno'>
-  <TabItem label="next-i18next" value="next-i18next">
+export const dynamicParams = false;
 
-```tsx fileName="next-i18next.config.js"
-module.exports = {
-  i18n: {
-    locales: ["en", "fr", "es"],
-    defaultLocale: "en",
-  },
-};
-```
+export function generateStaticParams() {
+  return locales.map((locale) => ({ locale }));
+}
 
-```tsx fileName="src/app/_app.tsx"
-import { appWithTranslation } from "next-i18next";
+export default function LocaleLayout({
+  children,
+  params,
+}: {
+  children: ReactNode;
+  params: { locale: string };
+}) {
+  const locale: Locale = (locales as readonly string[]).includes(params.locale)
+    ? (params.locale as any)
+    : defaultLocale;
 
-const MyApp = ({ Component, pageProps }) => <Component {...pageProps} />;
+  const dir = isRtl(locale) ? "rtl" : "ltr";
 
-export default appWithTranslation(MyApp);
+  return (
+    <html lang={locale} dir={dir}>
+      <body>{children}</body>
+    </html>
+  );
+}
 ```
 
-```tsx fileName="src/app/[locale]/about/page.tsx"
-import type { GetStaticProps } from "next";
-import { serverSideTranslations } from "next-i18next/serverSideTranslations";
-import { useTranslation } from "next-i18next";
-import { I18nextProvider, initReactI18next } from "react-i18next";
-import { createInstance } from "i18next";
-import { ClientComponent, ServerComponent } from "@components";
+```tsx fileName="src/app/[locale]/about.tsx"
+import I18nProvider from "@/components/I18nProvider";
+import { initI18next } from "@/app/i18n/server";
+import type { Locale } from "@/i18n.config";
+import ClientComponent from "@/components/ClientComponent";
+import ServerComponent from "@/components/ServerComponent";
 
-export default function HomePage() {
-  // Déclarez explicitement le namespace utilisé par ce composant
-  const resources = await loadMessagesFor(locale); // your loader (JSON, etc.)
+// Force static rendering for the page
+export const dynamic = "force-static";
 
-  const i18n = createInstance();
-  i18n.use(initReactI18next).init({
-    lng: locale,
-    fallbackLng: "en",
-    resources,
-    ns: ["common", "about"],
-    defaultNS: "common",
-    interpolation: { escapeValue: false },
-  });
+export default async function AboutPage({
+  params: { locale },
+}: {
+  params: { locale: Locale };
+}) {
+  const namespaces = ["common", "about"] as const;
 
-  const { t } = useTranslation("about");
+  const i18n = await initI18next(locale, [...namespaces]);
+  const tAbout = i18n.getFixedT(locale, "about");
 
   return (
-    <I18nextProvider i18n={i18n}>
+    <I18nProvider locale={locale} namespaces={[...namespaces]}>
       <main>
-        <h1>{t("title")}</h1>
+        <h1>{tAbout("title")}</h1>
+
         <ClientComponent />
-        <ServerComponent />
+        <ServerComponent t={tAbout} locale={locale} count={0} />
       </main>
-    </I18nextProvider>
+    </I18nProvider>
   );
 }
-
-export const getStaticProps: GetStaticProps = async ({ locale }) => {
-  // Ne préchargez que les namespaces nécessaires à CETTE page
-  return {
-    props: {
-      ...(await serverSideTranslations(locale ?? "en", ["common", "about"])),
-    },
-  };
-};
 ```
 
   </TabItem>
    <TabItem label="next-intl" value="next-intl">
 
-```tsx fileName="i18n.ts"
+```tsx fileName="src/i18n.ts"
 import { getRequestConfig } from "next-intl/server";
 import { notFound } from "next/navigation";
 
-// Can be imported from a shared config
-const locales = ["en", "fr", "es"];
+export const locales = ["en", "fr", "es"] as const;
+export const defaultLocale = "en" as const;
+
+async function loadMessages(locale: string) {
+  // Load only the namespaces your layout/pages need
+  const [common, about] = await Promise.all([
+    import(`../locales/${locale}/common.json`).then((m) => m.default),
+    import(`../locales/${locale}/about.json`).then((m) => m.default),
+  ]);
+
+  return { common, about } as const;
+}
 
 export default getRequestConfig(async ({ locale }) => {
-  // Validate that the incoming `locale` parameter is valid
   if (!locales.includes(locale as any)) notFound();
 
   return {
-    messages: (await import(`../messages/${locale}.json`)).default,
+    messages: await loadMessages(locale),
   };
 });
 ```
 
-```tsx fileName="src/app/[locale]/about/layout.tsx"
-import { NextIntlClientProvider } from "next-intl";
-import { getMessages } from "next-intl/server";
-import pick from "lodash/pick";
+```tsx fileName="src/app/[locale]/layout.tsx"
+import type { ReactNode } from "react";
+import { locales } from "@/i18n";
+import {
+  getLocaleDirection,
+  unstable_setRequestLocale,
+} from "next-intl/server";
+
+export const dynamic = "force-static";
+
+export function generateStaticParams() {
+  return locales.map((locale) => ({ locale }));
+}
 
 export default async function LocaleLayout({
   children,
   params,
 }: {
-  children: React.ReactNode;
-  params: { locale: string };
+  children: ReactNode;
+  params: Promise<{ locale: string }>;
 }) {
-  const { locale } = params;
-  // Les messages sont chargés côté serveur via src/i18n/request.ts
-  // (voir docs next-intl). Ici on ne pousse au client qu'un sous-ensemble
-  // utile aux composants client (optimisation du payload).
-  const messages = await getMessages();
-  const clientMessages = pick(messages, ["common", "about"]);
+  const { locale } = await params;
+
+  // Set the active request locale for this server render (RSC)
+  unstable_setRequestLocale(locale);
+
+  const dir = getLocaleDirection(locale);
 
   return (
-    <html lang={locale}>
-      <body>
-        <NextIntlClientProvider locale={locale} messages={clientMessages}>
-          {children}
-        </NextIntlClientProvider>
-      </body>
+    <html lang={locale} dir={dir}>
+      <body>{children}</body>
     </html>
   );
 }
 ```
 
 ```tsx fileName="src/app/[locale]/about/page.tsx"
-import { getTranslations } from "next-intl/server";
-import { ClientComponent, ServerComponent } from "@components";
+import { getTranslations, getMessages, getFormatter } from "next-intl/server";
+import { NextIntlClientProvider } from "next-intl";
+import pick from "lodash/pick";
+import ServerComponent from "@/components/ServerComponent";
+import ClientComponentExample from "@/components/ClientComponentExample";
+
+export const dynamic = "force-static";
 
-export default async function LandingPage({
+export default async function AboutPage({
   params,
 }: {
-  params: { locale: string };
+  params: Promise<{ locale: string }>;
 }) {
-  // Chargement strictement côté serveur (pas hydraté au client)
-  const t = await getTranslations("about");
+  const { locale } = await params;
+
+  // Messages are loaded server-side. Push only what's needed to the client.
+  const messages = await getMessages();
+  const clientMessages = pick(messages, ["common", "about"]);
+
+  // Strictly server-side translations/formatting
+  const tAbout = await getTranslations("about");
+  const tCounter = await getTranslations("about.counter");
+  const format = await getFormatter();
+
+  const initialFormattedCount = format.number(0);
 
   return (
-    <main>
-      <h1>{t("title")}</h1>
-      <ClientComponent />
-      <ServerComponent />
-    </main>
+    <NextIntlClientProvider locale={locale} messages={clientMessages}>
+      <main>
+        <h1>{tAbout("title")}</h1>
+        <ClientComponentExample />
+        <ServerComponent
+          formattedCount={initialFormattedCount}
+          label={tCounter("label")}
+          increment={tCounter("increment")}
+        />
+      </main>
+    </NextIntlClientProvider>
   );
 }
 ```
@@ -449,12 +719,16 @@ export default async function LandingPage({
   <TabItem label="intlayer" value="intlayer">
 
 ```tsx fileName="intlayer.config.ts"
-export default {
+import { type IntlayerConfig, Locales } from "intlayer";
+
+const config: IntlayerConfig = {
   internationalization: {
-    locales: ["en", "fr", "es"],
-    defaultLocale: "en",
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
   },
 };
+
+export default config;
 ```
 
 ```tsx fileName="src/app/[locale]/layout.tsx"
@@ -467,14 +741,16 @@ import {
 
 export const dynamic = "force-static";
 
-const LandingLayout: NextLayoutIntlayer = async ({ children, params }) => {
+const LocaleLayout: NextLayoutIntlayer = async ({ children, params }) => {
   const { locale } = await params;
 
   return (
     <html lang={locale} dir={getHTMLTextDir(locale)}>
-      <IntlayerClientProvider locale={locale}>
-        {children}
-      </IntlayerClientProvider>
+      <body>
+        <IntlayerClientProvider locale={locale}>
+          {children}
+        </IntlayerClientProvider>
+      </body>
     </html>
   );
 };
@@ -511,13 +787,13 @@ export default LandingPage;
 
 #### Comparison
 
-In comparison to other solutions, Intlayer uses plugins to optimize the import of content at build time.
+All three support per-locale content loading and providers.
 
-This means that the client context can be stored in the root layout, to reuse only one instance of the provider for all pages.
+- With **next-intl/next-i18next**, you typically load selected messages/namespaces per route and place providers where needed.
 
-In comparison, the other solutions require rebuilding a custom provider for each page.
+- With **Intlayer**, adds build-time analysis to infer usage, which can reduce manual wiring and may allow a single root provider.
 
-Intlayer also provides a Provider for your server components. We'll see why later.
+Choose between explicit control and automation based on team preference.
 
 ### Usage in a client component
 
@@ -526,10 +802,12 @@ Let's take an example of a client component rendering a counter.
 <Tab defaultTab="next-intl" group='techno'>
   <TabItem label="next-i18next" value="next-i18next">
 
-**Translations (must be real JSON in `public/locales/...`)**
+**Translations (one JSON per namespace under `src/locales/...`)**
 
-```json fileName="public/locales/en/about.json"
+```json fileName="src/locales/en/about.json"
 {
+  "title": "About",
+  "description": "About page description",
   "counter": {
     "label": "Counter",
     "increment": "Increment"
@@ -537,8 +815,10 @@ Let's take an example of a client component rendering a counter.
 }
 ```
 
-```json fileName="public/locales/fr/about.json"
+```json fileName="src/locales/fr/about.json"
 {
+  "title": "À propos",
+  "description": "Description de la page À propos",
   "counter": {
     "label": "Compteur",
     "increment": "Incrémenter"
@@ -546,19 +826,18 @@ Let's take an example of a client component rendering a counter.
 }
 ```
 
-**Client component**
+**Client component (loads only the required namespace)**
 
-```tsx fileName="src/components/ClientComponentExample.tsx"
+```tsx fileName="src/components/ClientComponent.tsx"
 "use client";
 
-import React, { useMemo, useState } from "react";
-import { useTranslation } from "next-i18next";
+import React, { useState } from "react";
+import { useTranslation } from "react-i18next";
 
-export default function ClientComponentExample() {
+const ClientComponent = () => {
   const { t, i18n } = useTranslation("about");
   const [count, setCount] = useState(0);
 
-  // next-i18next doesn't expose useNumber; use Intl.NumberFormat
   const numberFormat = new Intl.NumberFormat(i18n.language);
 
   return (
@@ -566,17 +845,19 @@ export default function ClientComponentExample() {
       <p>{numberFormat.format(count)}</p>
       <button
         aria-label={t("counter.label")}
-        onClick={() => setCount((count) => count + 1)}
+        onClick={() => setCount((c) => c + 1)}
       >
         {t("counter.increment")}
       </button>
     </div>
   );
-}
+};
+
+export default ClientComponent;
 ```
 
-> Don't forget to add "about" namespace on the page serverSideTranslations
-> We take here the version of react 19.x.x, but for lower versions, you will need to use useMemo to store the instance of the formatter as it's a heavy function
+> Ensure the page/provider includes only the namespaces you need (e.g. `about`).
+> If you use React < 19, memoize heavy formatters like `Intl.NumberFormat`.
 
   </TabItem>
   <TabItem label="next-intl" value="next-intl">
@@ -609,7 +890,7 @@ export default function ClientComponentExample() {
 import React, { useState } from "react";
 import { useTranslations, useFormatter } from "next-intl";
 
-export default function ClientComponentExample() {
+const ClientComponentExample = () => {
   // Scope directly to the nested object
   const t = useTranslations("about.counter");
   const format = useFormatter();
@@ -626,7 +907,7 @@ export default function ClientComponentExample() {
       </button>
     </div>
   );
-}
+};
 ```
 
 > Don't forget to add "about" message on the page client message
@@ -658,7 +939,7 @@ export default counterContent;
 import React, { useState } from "react";
 import { useNumber, useIntlayer } from "next-intlayer";
 
-export default function ClientComponentExample() {
+const ClientComponentExample = () => {
   const [count, setCount] = useState(0);
   const { label, increment } = useIntlayer("counter"); // returns strings
   const { number } = useNumber();
@@ -671,7 +952,7 @@ export default function ClientComponentExample() {
       </button>
     </div>
   );
-}
+};
 ```
 
   </TabItem>
@@ -701,65 +982,60 @@ We will take the case of a UI component. This component is a server component, a
 <Tab defaultTab="next-intl" group='techno'>
   <TabItem label="next-i18next" value="next-i18next">
 
-```tsx fileName="src/pages/about.tsx"
-import React from "react";
-import type { GetStaticProps } from "next";
-import { useTranslation } from "next-i18next";
-import { serverSideTranslations } from "next-i18next/serverSideTranslations";
-
+```tsx fileName="src/components/ServerComponent.tsx"
 type ServerComponentProps = {
-  count: number;
   t: (key: string) => string;
-  format: (value: number) => string;
+  locale: string;
+  count: number;
 };
 
-export default function ServerComponent({
-  t,
-  format,
-  count,
-}: ServerComponentProps) {
+const ServerComponent = ({ t, locale, count }: ServerComponentProps) => {
+  const formatted = new Intl.NumberFormat(locale).format(count);
+
   return (
     <div>
-      <p>{format(count)}</p>
+      <p>{formatted}</p>
       <button aria-label={t("counter.label")}>{t("counter.increment")}</button>
     </div>
   );
-}
-```
+};
 
-> As the server component cannot be async, you need to pass the translations and formatter function as props.
->
-> - `const { t, i18n } = useTranslation("about");`
-> - `const formatted = new Intl.NumberFormat(i18n.language).format(initialCount);`
+export default ServerComponent;
+```
 
   </TabItem>
   <TabItem label="next-intl" value="next-intl">
 
 ```tsx fileName="src/components/ServerComponent.tsx"
-import { getTranslations, getFormatter } from "next-intl/server";
+type ServerComponentProps = {
+  formattedCount: string;
+  label: string;
+  increment: string;
+};
 
-export default async function ServerComponent({
-  t,
-  format,
-  count,
-}: {
-  t: (key: string) => string;
-  format: (value: number) => string;
-  count: number;
-}) {
+const ServerComponent = ({
+  formattedCount,
+  label,
+  increment,
+}: ServerComponentProps) => {
   return (
     <div>
-      <p>{format.number(count)}</p>
-      <button aria-label={t("label")}>{t("increment")}</button>
+      <p>{formattedCount}</p>
+      <button aria-label={label}>{increment}</button>
     </div>
   );
-}
+};
+
+export default ServerComponent;
 ```
 
 > As the server component cannot be async, you need to pass the translations and formatter function as props.
 >
+> In your page / layout:
+>
+> - `import { getTranslations, getFormatter } from "next-intl/server";`
 > - `const t = await getTranslations("about.counter");`
-> - `const format = await getFormatter();`
+> - `const formatter = await getFormatter().then((formatter) => formatter.number());`
 
   </TabItem>
   <TabItem label="intlayer" value="intlayer">
@@ -767,7 +1043,11 @@ export default async function ServerComponent({
 ```tsx fileName="src/components/ServerComponent.tsx"
 import { useIntlayer, useNumber } from "next-intlayer/server";
 
-const ServerComponent = ({ count }: { count: number }) => {
+type ServerComponentProps = {
+  count: number;
+};
+
+const ServerComponent = ({ count }: ServerComponentProps) => {
   const { label, increment } = useIntlayer("counter");
   const { number } = useNumber();
 
@@ -832,10 +1112,9 @@ export async function generateMetadata({
 }): Promise<Metadata> {
   const { locale } = params;
 
-  // Dynamically import the correct JSON file
-  const messages = (
-    await import("@/../public/locales/" + locale + "/about.json")
-  ).default;
+  // Import the correct JSON bundle from src/locales
+  const messages = (await import("@/locales/" + locale + "/about.json"))
+    .default;
 
   const languages = Object.fromEntries(
     locales.map((locale) => [locale, localizedPath(locale, "/about")])
@@ -909,7 +1188,7 @@ export default function robots(): MetadataRoute.Robots {
 ```tsx fileName="src/app/[locale]/about/layout.tsx"
 import type { Metadata } from "next";
 import { locales, defaultLocale } from "@/i18n";
-import { getTranslations, unstable_setRequestLocale } from "next-intl/server";
+import { getTranslations } from "next-intl/server";
 
 function localizedPath(locale: string, path: string) {
   return locale === defaultLocale ? path : "/" + locale + path;
@@ -1061,149 +1340,126 @@ export default robots;
 
 > Intlayer provides a `getMultilingualUrls` function to generate multilingual URLs for your sitemap.
 
----
+### Middleware for locale routing
 
-## TypeScript & safety
-
-<Columns>
-  <Column>
-
-**next-intl**
-
-- Solid TypeScript support, but **keys aren’t strictly typed by default**; you’ll maintain safety patterns manually.
-
-  </Column>
-  <Column>
-
-**next-i18next**
-
-- Base typings for hooks; **strict key typing requires extra tooling/config**.
-
-  </Column>
-  <Column>
-
-**intlayer**
-
-- **Generates strict types** from your content. **IDE autocompletion** and **compile-time errors** catch typos and missing keys before deploy.
-
-  </Column>
-<Columns>
+<Tab defaultTab="next-intl" group='techno'>
+  <TabItem label="next-i18next" value="next-i18next">
 
-**Why it matters:** Strong typing shifts failures **left** (CI/build) instead of **right** (runtime).
+Add a middleware to handle locale detection and routing:
 
----
+```ts fileName="src/middleware.ts"
+import { NextResponse, type NextRequest } from "next/server";
+import { defaultLocale, locales } from "@/i18n.config";
 
-## Missing translation handling
+const PUBLIC_FILE = /\.[^/]+$/; // exclude files with extensions
 
-**next-intl**
+export function middleware(request: NextRequest) {
+  const { pathname } = request.nextUrl;
 
-- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+  if (
+    pathname.startsWith("/_next") ||
+    pathname.startsWith("/api") ||
+    pathname.startsWith("/static") ||
+    PUBLIC_FILE.test(pathname)
+  ) {
+    return;
+  }
 
-**next-i18next**
+  const hasLocale = locales.some(
+    (l) => pathname === "/" + l || pathname.startsWith("/" + l + "/")
+  );
+  if (!hasLocale) {
+    const locale = defaultLocale;
+    const url = request.nextUrl.clone();
+    url.pathname = "/" + locale + (pathname === "/" ? "" : pathname);
+    return NextResponse.redirect(url);
+  }
+}
 
-- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+export const config = {
+  matcher: [
+    // Match all paths except the ones starting with these and files with an extension
+    "/((?!api|_next|static|.*\\..*).*)",
+  ],
+};
+```
 
-**intlayer**
+  </TabItem>
+  <TabItem label="next-intl" value="next-intl">
 
-- **Build-time detection** with **warnings/errors** for missing locales or keys.
+Add a middleware to handle locale detection and routing:
 
-**Why it matters:** Catching gaps during build prevents “mystery strings” in production and aligns with strict release gates.
+```ts fileName="src/middleware.ts"
+import createMiddleware from "next-intl/middleware";
+import { locales, defaultLocale } from "@/i18n";
 
----
+export default createMiddleware({
+  locales: [...locales],
+  defaultLocale,
+  localeDetection: true,
+});
 
-## Routing, middleware & URL strategy
+export const config = {
+  // Skip API, Next internals and static assets
+  matcher: ["/((?!api|_next|.*\\..*).*)"],
+};
+```
 
-<Columns>
-  <Column>
+  </TabItem>
+  <TabItem label="intlayer" value="intlayer">
 
-**next-intl**
+Intlayer provides built-in middleware handling through the `next-intlayer` package configuration.
 
-- Works with **Next.js localized routing** on the App Router.
+  </TabItem>
+</Tab>
 
-  </Column>
-  <Column>
+### Setup checklist and good practices
 
-**next-i18next**
+<Tab defaultTab="next-intl" group='techno'>
+  <TabItem label="next-i18next" value="next-i18next">
 
-- Works with **Next.js localized routing** on the App Router.
+- Ensure `lang` and `dir` are set on the root `<html>` in `src/app/[locale]/layout.tsx`.
+- Split translations into namespaces (for example `common.json`, `about.json`) under `src/locales/<locale>/`.
+- Only load required namespaces in client components using `useTranslation('<ns>')` and by scoping `I18nProvider` with the same namespaces.
+- Keep pages static when possible: export `export const dynamic = 'force-static'` on pages; set `dynamicParams = false` and implement `generateStaticParams`.
+- Use sync server components nested under client boundaries by passing already-computed strings or the `t` function and the `locale`.
+- For SEO, set `alternates.languages` in metadata, list localized URLs in `sitemap.ts`, and disallow duplicate localized routes in `robots.ts`.
+- Prefer locale-aware formatters (e.g., `Intl.NumberFormat(locale)`) and memoize them on the client if using React < 19.
 
-  </Column>
-  <Column>
+  </TabItem>
+  <TabItem label="next-intl" value="next-intl">
 
-**intlayer**
+- **Set html `lang` and `dir`**: In `src/app/[locale]/layout.tsx`, compute `dir` via `getLocaleDirection(locale)` and set `<html lang={locale} dir={dir}>`.
+- **Split messages by namespace**: Organize JSON per locale and namespace (e.g., `common.json`, `about.json`).
+- **Minimize client payload**: On pages, send only required namespaces to `NextIntlClientProvider` (e.g., `pick(messages, ['common', 'about'])`).
+- **Prefer static pages**: Export `export const dynamic = 'force-static'` and generate static params for all `locales`.
+- **Synchronous server components**: Keep server components sync by passing precomputed strings (translated labels, formatted numbers) rather than async calls or non-serializable functions.
 
-- All of the above, plus **i18n middleware** (locale detection via headers/cookies) and **helpers** to generate localized URLs and `<link rel="alternate" hreflang="…">` tags.
+  </TabItem>
+  <TabItem label="intlayer" value="intlayer">
 
-  </Column>
-</Columns>
+- **Modular content**: Co-locate content dictionaries with components using `.content.{ts|js|json}` files.
+- **Type safety**: Leverage TypeScript integration for compile-time content validation.
+- **Build-time optimization**: Use Intlayer's build tools for automatic tree-shaking and bundle optimization.
+- **Integrated tooling**: Take advantage of built-in routing, SEO helpers, and visual editor support.
 
-**Why it matters:** Fewer custom glue layers; **consistent UX** and **clean SEO** across locales.
+  </TabItem>
+</Tab>
 
 ---
 
-## Server Components (RSC) alignment
-
-<Columns>
-  <Column>
-
-**next-intl**
-
-- Supports Next.js 13+. Often requires passing t-functions/formatters through component trees in hybrid setups.
-
-  </Column>
-  <Column>
-
-**next-i18next**
-
-- Supports Next.js 13+. Similar constraints with passing translation utilities across boundaries.
-
-  </Column>
-  <Column>
-
-**intlayer**
-
-- Supports Next.js 13+ and smooths the **server/client boundary** with a consistent API and RSC-oriented providers, avoiding shuttling formatters or t-functions.
-
-  </Column>
-</Columns>
-
-**Why it matters:** Cleaner mental model and fewer edge cases in hybrid trees.
-
----
+## And the winner is…
 
-## DX, tooling & maintenance
+It’s not simple. Each option has trade-offs. Here’s how I see it:
 
 <Columns>
   <Column>
 
-**next-intl**
-
-- Commonly paired with external localization platforms and editorial workflows.
-
-  </Column>
-  <Column>
-
 **next-i18next**
 
-- Commonly paired with external localization platforms and editorial workflows.
-
-  </Column>
-  <Column>
-
-**intlayer**
-
-- Ships a **free Visual Editor** and **optional CMS** (Git-friendly or externalized), plus a **VSCode extension** and **AI-assisted translations** using your own provider keys.
+- mature, full of features, lots of community plugins, but higher setup cost. If you need **i18next’s plugin ecosystem** (e.g., advanced ICU rules via plugins) and your team already knows i18next, accepting **more configuration** for flexibility.
 
   </Column>
-</Columns>
-
-**Why it matters:** Lowers ops cost and shortens the loop between developers and content authors.
-
-## And the winner is…
-
-It’s not simple. Each option has trade-offs. Here’s how I see it:
-
-<Columns>
   <Column>
 
 **next-intl**
@@ -1213,13 +1469,6 @@ It’s not simple. Each option has trade-offs. Here’s how I see it:
   </Column>
   <Column>
 
-**next-i18next**
-
-- mature, full of features, lots of community plugins, but higher setup cost. If you need **i18next’s plugin ecosystem** (e.g., advanced ICU rules via plugins) and your team already knows i18next, accepting **more configuration** for flexibility.
-
-  </Column>
-  <Column>
-
 **Intlayer**
 
 - built for modern Next.js, with modular content, type safety, tooling, and less boilerplate. If you value **component-scoped content**, **strict TypeScript**, **build-time guarantees**, **tree-shaking**, and **batteries-included** routing/SEO/editor tooling - especially for **Next.js App Router**, design-systems and **large, modular codebases**.
@@ -1233,8 +1482,6 @@ If you prefer minimal setup and accept some manual wiring, next-intl is a good p
 
 > **Future roadmap**: Intlayer also plans to develop plugins that work on top of **i18next** and **next-intl** solutions. This will give you the advantages of Intlayer for automation, syntax, and content management while keeping the security and stability provided by these established solutions in your application code.
 
----
-
 ## GitHub STARs
 
 GitHub stars are a strong indicator of a project's popularity, community trust, and long-term relevance. While not a direct measure of technical quality, they reflect how many developers find the project useful, follow its progress, and are likely to adopt it. For estimating the value of a project, stars help compare traction across alternatives and provide insights into ecosystem growth.