@intlayer/docs 9.4.3 → 9.5.0

package/docs/en/releases/v7.md

@@ -48,8 +48,6 @@ Welcome to Intlayer v7! This major release introduces significant improvements i
 - Smart chunking to handle large files within AI context limits
 - Automatic code formatting with configurable formatCommand
 
----
-
 ## Performance: Caching for faster builds
 
 Instead of rebuilding content declarations with esbuild on every build, v7 implements a caching strategy that speeds up the build process.
@@ -76,8 +74,6 @@ The new caching system:
 - Detects changes and rebuilds only modified files
 - Significantly reduces build times for large projects
 
----
-
 ## TypeScript: Locale-specific type generation
 
 TypeScript types are now generated per locale, providing stronger typing and eliminating union types across all locales.
@@ -102,8 +98,6 @@ Benefits:
 - Better type safety with no cross-locale type pollution
 - Improved performance by reducing type complexity
 
----
-
 ## Bundle optimization: Locales as strings
 
 The `Locales` type is no longer an enum, which means it's now fully tree-shakeable and won't bloat your bundle with thousands of unused locale records.
@@ -130,8 +124,6 @@ const locale: Locale = Locales.ENGLISH;
 
 See the [implementation details](https://github.com/aymericzip/intlayer/blob/main/packages/%40intlayer/types/src/index.ts) for more information.
 
----
-
 ## New routing modes for greater flexibility
 
 v7 introduces a unified `routing.mode` configuration that replaces the previous `prefixDefault` and `noPrefix` options, offering more granular control over URL structure.
@@ -162,8 +154,6 @@ export default {
 };
 ```
 
----
-
 ## GDPR compliance: localStorage / cookies storage
 
 v7 prioritizes user privacy by using `localStorage` as the default storage mechanism instead of cookies. This change helps with GDPR compliance by avoiding cookie consent requirements for locale preferences.
@@ -252,8 +242,6 @@ setLocale("en");
 **Note:** Cookies is enabled by default.
 **Note:** Check [GDPR cookie requirements](https://gdpr.eu/cookies/) for your specific use case.
 
----
-
 ## Visual Editor: 30% smaller package
 
 The Visual Editor package has been optimized to be 30% smaller than the previous version, thanks to:
@@ -264,8 +252,6 @@ The Visual Editor package has been optimized to be 30% smaller than the previous
 
 This results in faster download times and improved runtime performance for your application.
 
----
-
 ## Automatic Code Formatting: formatCommand configuration
 
 v7 introduces the `formatCommand` option in the editor configuration, allowing you to automatically format content files when they are written by Intlayer. This ensures consistent code style and formatting across your content declaration files.
@@ -323,8 +309,6 @@ formatCommand: 'bun format "{{file}}"';
 
 When Intlayer writes or updates a content declaration file (`.content.ts`, `.content.js`, etc.), it automatically runs the specified format command on the file. The `{{file}}` placeholder is replaced with the actual file path, and the command is executed in the project's base directory.
 
----
-
 ## Dictionary Configuration: Better organization and structure
 
 v7 introduces a new dedicated `dictionary` configuration section that provides better organization for dictionary-related settings and improved content management.
@@ -384,8 +368,6 @@ The dictionary section includes comprehensive properties for dictionary manageme
 
 For more information about content declaration files and how configuration values are applied, see the [Content File Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/content_file.md).
 
----
-
 ## Fill command: Updated behavior for better content management
 
 v7 introduces improved behavior for the `fill` command, providing more predictable and flexible content management:
@@ -471,8 +453,6 @@ const content = {
 };
 ```
 
----
-
 ## Enhanced stability and translation management
 
 v7 introduces several improvements to make content translation more reliable and efficient:
@@ -522,8 +502,6 @@ The system automatically:
 4. Validates and retries if needed
 5. Reconstructs the complete file
 
----
-
 ## Migration notes from v6
 
 ### Removed configurations
@@ -625,14 +603,10 @@ const content = {
 };
 ```
 
----
-
 ## Migration notes from v5 to v6
 
 Check the [migration notes from v5 to v6](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v6.md) for more information.
 
----
-
 ## Useful links
 
 - [Configuration Reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md)

package/docs/en/releases/v8.md

@@ -36,8 +36,6 @@ Welcome to Intlayer v8! This release focuses on enhancing developer experience w
 
 <TOC levels={[2]} maxDepth={1} />
 
----
-
 ## Rich Content Evolution: Markdown & HTML
 
 Intlayer v8 brings major improvements to how rich content is handled, introducing **HTML nodes** (which didn't exist in v7) and unifying the API with **Markdown nodes** (which existed in v7 but have been enhanced).
@@ -407,8 +405,6 @@ We have introduced new standalone renderer functions and components to give you
 
 For more details, see the [HTML Content Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/html.md) and [Markdown Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/markdown.md).
 
----
-
 ## YAML & Markdown Content Files (v8.10.0)
 
 You can now declare content directly using the `.content.md` and `.content.yaml` file extensions. This is perfect for long-form content, blogs, documentation, and privacy policies.
@@ -417,8 +413,6 @@ These files are fully editable from the Visual Editor, providing a streamlined w
 
 For more details, see the [YAML Content Files Documentation](https://intlayer.org/doc/concept/content#yaml-content-file) and [Markdown Content Files Documentation](https://intlayer.org/doc/concept/content/markdown).
 
----
-
 ## Custom URL Rewrites
 
 Intlayer v8 introduces support for **Custom URL Rewrites**, allowing you to define locale-specific paths that differ from the standard `/locale/path` structure. This is a powerful feature for improving local SEO and providing a more natural user experience for non-English speakers.
@@ -462,7 +456,7 @@ Intlayer v8 introduces support for **Custom URL Rewrites**, allowing you to defi
     ```
 
   </Tab>
-    <Tab label="React Router" value="reactrouter">
+  <Tab label="React Router" value="reactrouter">
 
     ```typescript fileName="intlayer.config.ts"
     import { Locales, type IntlayerConfig } from "intlayer";
@@ -588,8 +582,6 @@ This feature is supported out-of-the-box in **Next.js** and **Vite** through the
 
 For more information and integration guides, see the [Custom URL Rewrites Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/custom_url_rewrites.md).
 
----
-
 ### Enhanced Insertion Values
 
 In v8, insertion values can now **accept React elements (or Vue nodes)** in addition to strings and numbers. This allows you to inject rich, interactive components directly into your insertion templates.
@@ -813,8 +805,6 @@ const OpeningsComponent: FC<{ count: number }> = ({ count }) => {
 
 For more information, see the [Pluralization Documentation](https://intlayer.org/doc/concept/content/plural).
 
----
-
 ## Content Schema Validation
 
 Intlayer v8 introduces schema validation for dictionaries. You can now define reusable validation schemas in your configuration using Zod and apply them to your content files. This ensures your content always adheres to the expected structure, catching errors at build time.
@@ -857,8 +847,6 @@ export default aboutPageMetaContent;
 
 If the content doesn't match the schema (e.g., title is too short), the build process will raise an error.
 
----
-
 ## TypeScript: IntlayerNode Primitive Accessors
 
 The `IntlayerNode` type has been updated to allow calling primitive JavaScript methods directly on content nodes. This makes it possible to interact with your localized content directly as if it were a standard string, number, boolean, or array primitive.
@@ -885,8 +873,6 @@ content.myArrayOfString.find(...)   // Returns element
 content.myArrayOfString.join(', ')  // Returns joined string
 ```
 
----
-
 ### Enhanced Automatic Content Detection
 
 In v8, Intlayer intelligently detects Markdown syntax, HTML tags, and variable insertions in your content strings. This means you can often omit helper functions like `md()`, `html()`, or `insert()`.
@@ -960,8 +946,6 @@ The underlying JSON result remains the same, preserving the rich type informatio
 }
 ```
 
----
-
 ## Localization: new `useIntl` hook
 
 A new `useIntl()` hook is now available in React, Next.js and Vue. It provides a locale-bound `Intl` object that automatically uses the current language for formatting numbers, dates, and more, without needing to manually pass the locale.
@@ -1080,8 +1064,6 @@ A new `useIntl()` hook is now available in React, Next.js and Vue. It provides a
   </Tab>
 </Tabs>
 
----
-
 ## Tooling: VSCode Extension Enhancements
 
 The Intlayer VSCode extension receives major updates in v8 to streamline your internationalization workflow:
@@ -1090,8 +1072,6 @@ The Intlayer VSCode extension receives major updates in v8 to streamline your in
 - **Caching**: Enhanced caching layer for near-instant validation and autocompletion.
 - **Unused Keys & Duplicated Keys Detection**: New features to automatically detect **unused keys** and **duplicated keys** across your dictionaries, helping you keep your content clean and efficient.
 
----
-
 ## Tooling: C++ Watcher & OXC-based LSP (v8.12.0)
 
 Intlayer v8.12.0 brings major improvements to the developer experience:
@@ -1101,15 +1081,13 @@ Intlayer v8.12.0 brings major improvements to the developer experience:
 
 For more details, see the [LSP Documentation](https://intlayer.org/doc/lsp).
 
----
-
 ## Compiler Optimizations
 
 Intlayer v8 includes a new caching layer for the Markdown and HTML compiler. This ensures that identical content strings with the same configuration are only parsed once, significantly reducing the overhead during re-renders or when using the same content in multiple places.
 
 <Tabs group='bundler'>
   <Tab label="Next.js" value="nextjs">
-  
+
     ```typescript fileName="babel.config.js"
       const {
       intlayerExtractBabelPlugin,
@@ -1131,7 +1109,7 @@ Intlayer v8 includes a new caching layer for the Markdown and HTML compiler. Thi
 
   </Tab>
   <Tab label="Vite" value="vite">
-   
+
     ```typescript fileName="vite.config.js"
     import { defineConfig } from 'vite';
     import { intlayer, intlayerCompiler } from "vite-intlayer";
@@ -1156,8 +1134,6 @@ Intlayer v8 includes a new caching layer for the Markdown and HTML compiler. Thi
   </Tab>
 </Tabs>
 
----
-
 ## Experimental Build Optimizations: Minify & Purge (v8.7.0)
 
 Intlayer v8.7.0 introduces new experimental build features in your `intlayer.config.ts` designed to optimize your production bundle:
@@ -1198,8 +1174,6 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
----
-
 ## Flexibility: Unified Import Mode
 
 The `live` boolean property has been deprecated in favor of a more comprehensive `importMode` property. This allows for explicit definition of how dictionaries should be loaded: statically, dynamically, or via live sync.
@@ -1240,8 +1214,6 @@ export default {
 }
 ```
 
----
-
 ## Dictionary Location Control
 
 v8 introduces the `location` property to explicitly manage where dictionaries live and how they synchronize. This is particularly useful for hybrid workflows involving both local files and remote CMS content.
@@ -1262,8 +1234,6 @@ export default {
 }
 ```
 
----
-
 ## System Configuration Separation
 
 Intlayer v8 separates the configuration of content sources from internal system and output paths. This declutters the `content` property and makes it clear which settings are intended for user management vs. those that are managed by the Intlayer system.
@@ -1303,8 +1273,6 @@ export default {
 };
 ```
 
----
-
 ## Content and Code Directory Separation
 
 Intlayer v8 separates the configuration for content definition files from the configuration for code transformation. This allows for more precise watching and scanning, improving build performance.
@@ -1339,22 +1307,16 @@ export default {
 };
 ```
 
----
-
 ## Framework: Svelte Improvements
 
 Markdown and HTML content in Svelte now automatically parse to HTML when stringified. This makes it much easier to use with Svelte's `{@html}` syntax, as you can now simply pass the content node directly.
 
----
-
 ## Angular Support: Vite Bundler (v8.11.0)
 
 For Angular users, Intlayer now natively supports the Vite bundler through a new custom esbuild plugin, speeding up development and build times.
 
 For details on configuration, see the [Angular Environment Documentation](https://intlayer.org/doc/environment/angular).
 
----
-
 ## Sitemap Generation (v8.6.0)
 
 Intlayer now generates sitemaps automatically based on your locales and routing mode. This is particularly useful for SEO optimization in router architectures like TanStack Router:
@@ -1388,8 +1350,6 @@ export const Route = createFileRoute("/sitemap.xml")({
 });
 ```
 
----
-
 ## Migration notes from v7
 
 ### Configuration Changes
@@ -1399,8 +1359,6 @@ export const Route = createFileRoute("/sitemap.xml")({
 - **`contentDir` and `codeDir`**: `contentDir` is now specifically for content files. A new `codeDir` property has been added for code transformation. If `codeDir` is not set, Intlayer will fallback to `contentDir` and log a warning.
 - **Schema Validation**: To use the new `schema` feature, ensure you have `zod` installed in your project.
 
----
-
 ## Useful links
 
 - [Configuration Reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md)

package/docs/en/releases/v9.md

@@ -45,8 +45,6 @@ Welcome to Intlayer v9! This major release marks a huge milestone in simplifying
 
 <TOC levels={[2]} maxDepth={1} />
 
----
-
 ## Compat Adapter Packages
 
 Migrating to Intlayer from popular i18n libraries is now easier than ever. We have created five compat packages that expose the **exact same public APIs** as standard i18n libraries but delegate all translation work to Intlayer at runtime.
@@ -107,8 +105,6 @@ export default defineConfig({
 });
 ```
 
----
-
 ## Mutualized Runtime Resolver
 
 All compat adapters now route translation resolution through a single, highly optimized runtime parser: `@intlayer/core/messageFormat`.
@@ -117,8 +113,6 @@ All compat adapters now route translation resolution through a single, highly op
 - **Message Node Resolver**: Resolves nested nodes: `insert()`, `plural()` (CLDR plural rules), `enu()` (enumeration), `gender()`, HTML tags, arrays, and callable function nodes.
 - **Tokenized Tag Parser**: Supports inline XML/HTML tags and numbered tags (e.g., `<1>children</1>`) to power rich-text rendering out of the box.
 
----
-
 ## Feature Spec: Collections & Variants
 
 Intlayer v9 expands beyond static key-value objects, allowing dictionaries to declare dynamic layout structures that are fully typed end-to-end.
@@ -214,8 +208,6 @@ const product = useIntlayer("product-copy", {
 });
 ```
 
----
-
 ## `@intlayer/analytics`: content exposure tracking & A/B testing
 
 A new optional package, [`@intlayer/analytics`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/analytics.md), tells you which content is actually shown to your visitors — and closes the loop on **Collections & Variants** by letting you A/B test content and measure conversions per variant.
@@ -257,8 +249,6 @@ npm install @intlayer/analytics
 
 Available today for React, Next.js, and React Native (via `react-intlayer`); other framework bindings (Vue, Svelte, Angular, …) are planned, following the same rollout pattern as `@intlayer/editor`. See the [Analytics documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/analytics.md) for the full guide.
 
----
-
 ## Vite Plugin: Bundled Compiler & Proxy
 
 The `intlayer()` Vite plugin now bundles the **compiler** and the **locale-routing proxy** directly, so most projects only need a single plugin in `vite.config.ts`:
@@ -293,8 +283,6 @@ export default config;
 
 The standalone `intlayerCompiler()` and `intlayerProxy()` plugins remain exported for advanced setups. Registering them alongside `intlayer()` is safe — each plugin deduplicates itself and runs only once.
 
----
-
 ## Compiler disabled by default
 
 Starting with Intlayer v9, the **compiler is disabled by default** (`compiler.enabled` now defaults to `false`). To opt in to build-time extraction of your `.content.ts` files, set `compiler.enabled: true` in your configuration:
@@ -314,8 +302,6 @@ export default config;
 
 When the compiler is disabled, Intlayer skips the build-time extraction step and relies on your already-declared dictionaries. Enable it only when you want the bundler plugin (`@intlayer/swc`, `@intlayer/babel`, or the `intlayer()` Vite plugin) to extract content automatically.
 
----
-
 ## React Native: single-package imports
 
 In a React Native or Expo app, you no longer need to juggle both `react-intlayer` and `react-native-intlayer`. The `react-native-intlayer` package now **re-exports the full `react-intlayer` API** (hooks, utilities, and the `/format`, `/html`, and `/markdown` subpaths), and its `IntlayerProvider` automatically applies the React Native polyfills.
@@ -336,8 +322,6 @@ npm install intlayer react-native-intlayer
 
 > Importing from `react-intlayer` keeps working, but `react-native-intlayer` is now the recommended single entry point for React Native — its provider ships the polyfills the web-oriented `react-intlayer` provider does not.
 
----
-
 ## CMS SDK: use Intlayer as a headless content database
 
 Intlayer v9 ships a clean, auto-authenticating SDK in `@intlayer/api` to interact with the CMS programmatically — fetch projects, fetch dictionaries, and push or update them from your own server, scripts, or CI. Authentication (OAuth2 `client_credentials`) is handled and refreshed for you.
@@ -362,8 +346,6 @@ await dictionaryEndpoint(cms).pushDictionaries([myDictionary]);
 
 > Security: the CMS credentials grant write access to your content. Only ever create the authenticator on the **server side** — never ship `clientId` / `clientSecret` to the browser.
 
----
-
 ## Self-Hosting
 
 Intlayer v9 ships first-class support for running your own Intlayer instance with a single command. No Intlayer Cloud account required.
@@ -374,8 +356,6 @@ curl -fsSL https://intlayer.org/install.sh | sh
 
 The installer downloads a `docker-compose.yml` and a `.env`, auto-generates the required secrets, and runs `docker compose up -d`. Everything — the dashboard, the API, the database, object storage, and transactional email — runs locally in containers.
 
----
-
 ## Migration notes from v8
 
 If you are upgrading from v8, note that the v9 does not include breaking changes. But here are the key changes:
@@ -386,8 +366,6 @@ If you are upgrading from v8, note that the v9 does not include breaking changes
 - **Custom Selectors**: When calling `useIntlayer`, the second parameter is now reserved for an option object containing `{ locale, item, variant }`. If you previously passed a locale string directly, you can still do so, but using the options object is recommended for advanced selections.
 - **React Native**: `react-native-intlayer` now re-exports the entire `react-intlayer` API. In a React Native app, import everything from `react-native-intlayer` and drop the direct `react-intlayer` dependency. Existing `react-intlayer` imports continue to work.
 
----
-
 ## Useful links
 
 - [Compat Adapter Packages Guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/index.md)

package/docs/en/roadmap.md

@@ -30,14 +30,10 @@ author: aymericzip
 
 Intlayer is a content management and internationalization solution designed to streamline how you declare, manage, and update content across your applications. It offers powerful features such as centralized or distributed content declaration, extensive internationalization options, Markdown support, conditional rendering, TypeScript/JavaScript/JSON integration, and more. Below is a comprehensive overview of what Intlayer currently provides, followed by upcoming roadmap features.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Current Features
 
 ### 1. Content Declaration
@@ -149,8 +145,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [Build Configuration](https://intlayer.org/doc/concept/configuration#build-configuration)
 
----
-
 ## Integration with Frameworks & Environments
 
 ### 1. Next.js
@@ -237,8 +231,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [Preact](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_preact.md)
 
----
-
 ## Visual Editors and CMS
 
 ### 1. Local Visual Editor
@@ -264,21 +256,15 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
 
----
-
 ## IDE Extensions
 
 - Extensions for major IDEs to provide a **graphical interface** for managing local and remote translations.
 - Features could include auto-generating content declaration files for components, direct integration with the Intlayer CMS, and real-time validation.
 
----
-
 ## MCP Server
 
 - A **MCP server** that allows you to manage your content and translations using an integrated tool in your IDE.
 
----
-
 ## Intlayer CLI
 
 - **Translation and file generation**: Run audits on your content files to generate missing translations and review inconsistencies.
@@ -289,15 +275,11 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CLI](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md)
 
----
-
 ## Environments
 
 - Use **environment variables** to configure Intlayer differently across production, testing, and local environments.
 - Define which visual editor or remote CMS project to target depending on your environment.
 
----
-
 ## Hot Content Updates
 
 - When using remote dictionaries and the Intlayer CMS, you can **update your application’s content on the fly**, without needing to redeploy.
@@ -306,8 +288,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
 
----
-
 ## Upcoming Features
 
 ### 1. A/B Testing & Personalization
@@ -336,8 +316,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 - Efforts are underway to support **Solid, Svelte, Angular**, and more.
 - Aim to make Intlayer compatible with **any JavaScript-powered application**.
 
----
-
 ## Conclusion
 
 Intlayer aims to be a one-stop solution for content management and internationalization. It focuses on flexibility (centralized or distributed files), broad language support, easy integration with modern frameworks and bundlers, and powerful AI-driven features. As new capabilities, such as A/B testing, versioning, and automated translations, become available, Intlayer will continue to simplify content workflows and elevate user experiences across different platforms.

package/docs/en/self_hosting.md

@@ -34,8 +34,6 @@ The only external dependency is **MongoDB**: the backend connects to a MongoDB *
 
 <TOC/>
 
----
-
 ## Architecture
 
 ```
@@ -55,8 +53,6 @@ The only external dependency is **MongoDB**: the backend connects to a MongoDB *
 
 Chromium (used for Puppeteer screenshot generation) is bundled inside the image. No separate container is needed. Redis and MinIO run inside the container. MongoDB is **not** hosted by the image; the backend connects to your Atlas cluster over `mongodb+srv://`.
 
----
-
 ## Prerequisites
 
 - **Docker** ≥ 24. The installer offers to install it for you if it is missing (via [get.docker.com](https://get.docker.com) on Linux, Homebrew on macOS).
@@ -67,8 +63,6 @@ Chromium (used for Puppeteer screenshot generation) is bundled inside the image.
 
 Everything else — Bun, Redis, MinIO, Chromium — ships inside the image.
 
----
-
 ## Quick start
 
 ### 1. Run the installer
@@ -137,8 +131,6 @@ curl -fsSL https://intlayer.org/install.sh | INTLAYER_ENV_FILE=./config/intlayer
 
 > The four port variables only change the **host** side of the mapping printed in the `docker run` command. The published image has `http://localhost:3000`, `http://localhost:3100` and `http://localhost:9000` compiled into the dashboard bundle at build time, so remapping them leaves the browser pointing at the old ports. Keep the defaults unless you are building your own image — see [Limitations](#limitations).
 
----
-
 ## First-run setup
 
 On a fresh instance (empty database), opening the dashboard redirects you to the **`/init`** page:
@@ -149,8 +141,6 @@ On a fresh instance (empty database), opening the dashboard redirects you to the
 
 Once an admin exists, `/init` redirects to the standard sign-in page.
 
----
-
 ## Services
 
 | Service     | Location           | Host port(s)                  | Purpose                                                       |
@@ -163,8 +153,6 @@ Once an admin exists, `/init` redirects to the standard sign-in page.
 
 > MinIO port `9000` must be reachable by the browser because uploaded assets (avatars, screenshots) are loaded directly from `S3_PUBLIC_URL=http://localhost:9000/intlayer`.
 
----
-
 ## Environment variables
 
 ### Required
@@ -222,8 +210,6 @@ Set `MAIL_PROVIDER` to activate it. When unset, the default Resend mailer is use
 
 > Precedence: an organization's own mailer (configured from the **Organization** dashboard) takes priority over the global mailer, which in turn takes priority over the default Resend key.
 
----
-
 ## Connecting your Intlayer project
 
 Once the stack is running, point your project at the self-hosted backend and dashboard instead of `intlayer.org`.
@@ -285,8 +271,6 @@ const cms = createIntlayerCMS({
 const { data: dictionaries } = await dictionaryEndpoint(cms).getDictionaries();
 ```
 
----
-
 ## Upgrading
 
 Re-run the installer to pull the latest image, then recreate the container. Your `intlayer.env` is left untouched, and your data is preserved in the named volume (MinIO/Redis) and in your Atlas cluster (MongoDB):
@@ -297,8 +281,6 @@ docker rm -f intlayer
 # re-run the `docker run …` command from step 3 of Quick start
 ```
 
----
-
 ## Backup and restore
 
 MongoDB data lives in your Atlas cluster — back it up with Atlas' own tools. The bundled local datastores live under the `intlayer-data` volume.
@@ -321,16 +303,12 @@ docker run --rm \
   busybox tar xzf /backup/intlayer-data.tar.gz -C /
 ```
 
----
-
 ## Limitations
 
 - **MongoDB must be external (Atlas).** The backend connects only over `mongodb+srv://` (built from `DB_ID` / `DB_MDP` / `DB_CLUSTER`), so a plain `mongodb://host:27017` — including the container's own bundled `mongod` — cannot be used. Provide a MongoDB Atlas cluster.
 - **No custom domain, and no port remapping.** All browser-facing `VITE_*` URLs are inlined into the app at build time, and the published image ships with `localhost` values. The dashboard must be accessed at `http://localhost:3000`, the API at `:3100` and MinIO at `:9000`; serving it on a public domain — or on different ports — would require rebuilding the image with the target URLs baked in (`--build-arg VITE_BACKEND_URL=…`) and is not supported out of the box.
 - **Email requires a working mailer.** First-run setup enforces email verification, so either `RESEND_API_KEY` or a [global SMTP mailer](#global-mailer) (`MAIL_PROVIDER=smtp` + `MAIL_SMTP_*`) must be configured. After the first admin signs in, each organization can also configure its own SMTP or Resend mailer from the dashboard.
 
----
-
 ## Troubleshooting
 
 ### Dashboard loads but the API resets the connection (`ERR_CONNECTION_RESET` on `:3100`)
@@ -356,8 +334,6 @@ The `init-minio` one-shot creates the bucket on first boot. If assets fail to lo
 docker restart intlayer
 ```
 
----
-
 ## Useful links
 
 - [Intlayer CMS documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)

package/docs/en/testing.md

@@ -27,16 +27,12 @@ author: aymericzip
 
 This guide shows how to automatically verify your dictionaries are complete, catch missing translations before shipping, and test localized UI in your app.
 
----
-
 ## What you can test
 
 - **Missing translations**: fail CI if any required locales are missing for any dictionary.
 - **Localized UI rendering**: render components with a specific locale provider and assert on visible text/attributes.
 - **Build-time audits**: run a quick audit locally via CLI.
 
----
-
 ## Quick start: audit via CLI
 
 Run the audit from your project root:
@@ -68,8 +64,6 @@ Useful flags:
 
 Note: the CLI prints a detailed report but does not exit non‑zero on failures. For CI gating, add a unit test (below) that asserts zero missing required locales.
 
----
-
 ## Programmatic test (Vitest/Jest)
 
 Use the Intlayer CLI API to assert there are no missing translations for your required locales.
@@ -117,8 +111,6 @@ How it works:
   - `missingLocales`: union of all missing locales.
   - `missingRequiredLocales`: subset limited to `requiredLocales` (or all locales if `requiredLocales` is not set).
 
----
-
 ## Testing localized UI (React / Next.js)
 
 Render components under an Intlayer provider and assert on visible content.
@@ -165,8 +157,6 @@ Tips:
 - When you need raw string values for attributes (e.g., `aria-label`), access the `.value` field returned by `useIntlayer` in React.
 - Keep dictionaries colocated with components for easier unit testing and cleanup.
 
----
-
 ## Continuous Integration
 
 Add a test that fails the build when required translations are missing.
@@ -216,8 +206,6 @@ pnpm intlayer content test --verbose
 bun x intlayer content test --verbose
 ```
 
----
-
 ## Troubleshooting
 
 - Ensure your Intlayer configuration defines `locales` and (optionally) `requiredLocales`.

package/docs/en-GB/analytics.md

@@ -35,8 +35,6 @@ author: aymericzip
 
 <TOC/>
 
----
-
 ## What it tracks
 
 `@intlayer/analytics` batches three kinds of anonymous events:

package/docs/en-GB/bundle_optimization.md

@@ -133,8 +133,6 @@ During `next build`, `withIntlayer` analyses your sources, rewrites the compiled
 
 > Purge and minify run on `next build` only — the optimise pipeline is off during `next dev`.
 
-> They are also disabled when compat-adapter callers are configured (`swcExtraCallers`, set by the compat packages such as `@intlayer/next-intl` or `@intlayer/react-i18next`): those call sites are invisible to the usage analyser, so purging would remove fields the code still reads. Import rewriting stays active.
-
 **Earlier versions (before 9.2.1)** required `@intlayer/babel` and a `babel.config.js` declaring `intlayerPurgeBabelPlugin` and `intlayerMinifyBabelPlugin`. That file is no longer needed and can be deleted.
 
  </Tab>