@intlayer/docs 9.4.3 → 9.5.0

package/docs/en/packages/intlayer/getDictionary.md

@@ -41,8 +41,6 @@ Unlike [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/doc
 - Fully typed: the returned object mirrors the `content` you passed
 - Accepts custom interpreter plugins
 
----
-
 ## Function Signature
 
 ```typescript
@@ -53,8 +51,6 @@ getDictionary(
 ): DeepTransformContent<...>
 ```
 
----
-
 ## Parameters
 
 - `dictionary: Dictionary | QualifiedDictionaryGroup`
@@ -77,8 +73,6 @@ getDictionary(
 - **Type**: The interpreted content of the dictionary.
 - **Description**: The `content` you passed, with every Intlayer node resolved for the requested locale. For a collection group without an `item` selector, an ordered array of interpreted entries is returned; `null` is returned when the selector targets nothing.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -126,16 +120,12 @@ const secondItem = getDictionary(blogPostGroup, { item: 2, locale: "fr" });
 const allItems = getDictionary(blogPostGroup, { locale: "fr" });
 ```
 
----
-
 ## Related Functions
 
 - [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayer.md): Same interpretation, but the dictionary is looked up by key in the generated registry.
 - [`getDictionaryAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getDictionaryAsync.md): Counterpart for per-locale loader maps.
 - [`useDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/react-intlayer/useDictionary.md): The React hook equivalent, reading the locale from the provider.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en/packages/intlayer/getDictionaryAsync.md

@@ -44,8 +44,6 @@ It is the counterpart of [`getDictionary`](https://github.com/aymericzip/intlaye
 - Deduplicates concurrent loads of the same chunk, and caches the resolved content
 - Failed loads are evicted from the cache so a later call retries the chunk
 
----
-
 ## Function Signature
 
 ```typescript
@@ -57,8 +55,6 @@ getDictionaryAsync(
 ): Promise<DeepTransformContent<...>>
 ```
 
----
-
 ## Parameters
 
 - `dictionaryLoaders: PlainDynamicLoaderMap | QualifiedDynamicLoaderMap`
@@ -86,8 +82,6 @@ getDictionaryAsync(
 - **Type**: `Promise<Content>` — a promise resolving to the interpreted content of the loaded chunk.
 - **Description**: Resolves to `null` when the map emits no chunk for the requested locale nor for any of its fallbacks, mirroring how a missing qualified coordinate resolves.
 
----
-
 ## Example Usage
 
 ### With a generated loader map
@@ -123,8 +117,6 @@ const promoBanner = await getDictionaryAsync(bannerLoaderMap, "banner", {
 });
 ```
 
----
-
 ## Behaviour Notes
 
 ### Caching and deduplication
@@ -135,16 +127,12 @@ The cache stores the **promise** of each `key + locale + selector` triple, so co
 
 A plain loader map is walked along the same fallback chain as the synchronous mode: the requested locale first, then its fallbacks, then `null` if none emitted a chunk.
 
----
-
 ## Related Functions
 
 - [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayerAsync.md): The function applications call; build plugins rewrite it into `getDictionaryAsync`.
 - [`getDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getDictionary.md): Synchronous counterpart taking a full dictionary.
 - [Dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md): Collections and variants, and the loader maps they generate.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en/packages/intlayer/getIntlayer.md

@@ -42,8 +42,6 @@ It reads the dictionaries generated by Intlayer in `.intlayer/`, so the `key` ar
 - Results are memoized per `key + locale + selector`
 - Falls back to a safe proxy in development when a dictionary is missing, instead of crashing
 
----
-
 ## Function Signature
 
 ```typescript
@@ -54,8 +52,6 @@ getIntlayer(
 ): DeepTransformContent<...>
 ```
 
----
-
 ## Parameters
 
 - `key: DictionaryKeys`
@@ -83,8 +79,6 @@ getIntlayer(
 - **Type**: The interpreted content of the dictionary, typed from your declaration.
 - **Description**: A plain object mirroring the `content` field of your dictionary, where every Intlayer node has been resolved to its final value for the requested locale.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -152,8 +146,6 @@ const allPosts = getIntlayer("blog-post", { locale: "fr" });
 const banner = getIntlayer("banner", { variant: "black-friday", locale: "fr" });
 ```
 
----
-
 ## Behaviour Notes
 
 ### Caching
@@ -168,16 +160,12 @@ In development, requesting a key that has no generated dictionary logs a warning
 
 `getIntlayer` reads the merged dictionary, which holds **every** locale. In client bundles, the [build plugins](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/bundle_optimization.md) rewrite the call so only the required content is shipped. When you read content outside of rendering (metadata, loaders, server functions) and want a single locale loaded on demand, use [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayerAsync.md) instead.
 
----
-
 ## Related Functions
 
 - [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayerAsync.md): Async counterpart loading a single locale chunk.
 - [`getDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getDictionary.md): Interprets a dictionary object you pass yourself, instead of one looked up by key.
 - [`useIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/react-intlayer/useIntlayer.md): The React hook equivalent, reading the locale from the provider.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en/packages/intlayer/getIntlayerAsync.md

@@ -46,8 +46,6 @@ Without those plugins — an unoptimized build — the call resolves through the
 - Concurrent calls for the same chunk share a single load
 - Safe to use in `async` metadata builders, loaders and server functions
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +56,6 @@ getIntlayerAsync(
 ): Promise<DeepTransformContent<...>>
 ```
 
----
-
 ## Parameters
 
 - `key: DictionaryKeys`
@@ -86,8 +82,6 @@ getIntlayerAsync(
 
 - **Type**: `Promise<Content>` — a promise resolving to the interpreted content of the dictionary, typed from your declaration.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -98,8 +92,6 @@ import { getIntlayerAsync } from "intlayer";
 const { title } = await getIntlayerAsync("app", "fr"); // "Bonjour"
 ```
 
----
-
 ## `getIntlayer` vs `getIntlayerAsync`
 
 |                    | [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayer.md) | `getIntlayerAsync`                                |
@@ -111,16 +103,12 @@ const { title } = await getIntlayerAsync("app", "fr"); // "Bonjour"
 
 Both accept the same arguments and return the same content: switching from one to the other only changes **when** and **how much** is loaded.
 
----
-
 ## Related Functions
 
 - [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getIntlayer.md): Synchronous equivalent reading the merged dictionary.
 - [`getDictionaryAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getDictionaryAsync.md): The lower-level function the build plugins rewrite this call into.
 - [`getLocale`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocale.md): Detects the locale of an incoming request.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en/packages/intlayer/getLocalizedPath.md

@@ -44,8 +44,6 @@ It is the relative counterpart of [`getLocalizedUrl`](https://github.com/aymeric
 - Automatically handles fallback to the canonical path if no rewrite rule is found for the specified locale.
 - Narrows its return type: a literal path resolves to the localized string literal at compile time.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -61,8 +59,6 @@ getLocalizedPath(
 ): string
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -88,8 +84,6 @@ getLocalizedPath(
   - `options.mode?: 'prefix-no-default' | 'prefix-all' | 'no-prefix' | 'search-params'` — how the locale appears in the path. **Default**: `configuration.routing.mode`
   - `options.rewrite?: RoutingConfig['rewrite']` — custom rewrite rules. **Default**: `configuration.routing.rewrite`
 
----
-
 ## Returns
 
 - **Type**: `string`
@@ -117,8 +111,6 @@ Two cases stay widened to `string`, because they cannot be resolved at compile t
 - a path that is not a string literal (e.g. one built from a variable);
 - a path matched by a rule using a multi-segment or optional parameter (`[...slug]`, `[[...slug]]`, `:param?`).
 
----
-
 ## Example Usage
 
 ### Basic Usage (With Configuration)
@@ -177,8 +169,6 @@ getLocalizedPath("/about");
 // Output: "/about"
 ```
 
----
-
 ## Related Functions
 
 - [`getCanonicalPath`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getCanonicalPath.md): Resolves a localized path back to its internal canonical path. Note that it undoes the rewrite rules only — strip the locale prefix with [`getPathWithoutLocale`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getPathWithoutLocale.md) first.

package/docs/en/packages/intlayer/getLocalizedUrl.md

@@ -42,8 +42,6 @@ The `getLocalizedUrl` function generates a localized URL by prefixing the given
 - Can be used with minimal parameters for simple cases or fully customized for complex scenarios
 - Supports multiple routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +56,6 @@ getLocalizedUrl(
 ): string
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -106,8 +102,6 @@ getLocalizedUrl(
 - **Type**: `string`
 - **Description**: The localized URL for the specified locale.
 
----
-
 ## Example Usage
 
 ### Basic Usage (Only Required Parameters)
@@ -217,8 +211,6 @@ getLocalizedUrl("/about", Locales.ITALIAN, {
 // Output: "/about" (no prefix applied for unsupported locale)
 ```
 
----
-
 ## Edge Cases
 
 - **No Locale Segment:**
@@ -237,8 +229,6 @@ getLocalizedUrl("/about", Locales.ITALIAN, {
   - `'no-prefix'`: No locale prefixes in URLs (locale handled elsewhere)
   - `'search-params'`: Locale specified via query parameter (e.g., `/about?locale=fr`)
 
----
-
 ## Usage in Applications
 
 In a multilingual application, configuring the internationalization settings with `locales` and `defaultLocale` is critical for ensuring the correct language is displayed. Below is an example of how `getLocalizedUrl` can be used in an application setup:

package/docs/en/packages/intlayer/getMultilingualUrls.md

@@ -42,8 +42,6 @@ The `getMultilingualUrls` function generates a mapping of multilingual URLs by p
 - Supports multiple routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 - Returns a mapping object with all locales as keys and their corresponding URLs as values
 
----
-
 ## Function Signature
 
 ```typescript
@@ -57,8 +55,6 @@ getMultilingualUrls(
 ): StrictModeLocaleMap<string>
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -100,8 +96,6 @@ getMultilingualUrls(
 - **Type**: `StrictModeLocaleMap<string>`
 - **Description**: An object mapping each locale to its corresponding multilingual URL.
 
----
-
 ## Example Usage
 
 ### Basic Usage (Uses Project Configuration)
@@ -200,8 +194,6 @@ getMultilingualUrls("/dashboard", {
 // }
 ```
 
----
-
 ## Edge Cases
 
 - **No Locale Segment:**
@@ -220,8 +212,6 @@ getMultilingualUrls("/dashboard", {
   - `'no-prefix'`: No locale prefixes in URLs (all locales return same URL)
   - `'search-params'`: Locale specified via query parameter (e.g., `/dashboard?locale=fr`)
 
----
-
 ## Usage in Applications
 
 In a multilingual application, configuring the internationalization settings with `locales` and `defaultLocale` is critical for ensuring the correct language is displayed. Below is an example of how `getMultilingualUrls` can be used in an application setup:

package/docs/en/packages/intlayer/getPrefix.md

@@ -39,8 +39,6 @@ The `getPrefix` function determines the URL prefix for a given locale based on t
 - Supports all routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 - Lightweight utility for determining when to add locale prefixes
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +56,6 @@ type GetPrefixResult = {
 }
 ```
 
----
-
 ## Parameters
 
 - `locale: Locales`
@@ -94,8 +90,6 @@ type GetPrefixResult = {
   - `prefix`: The path prefix with trailing slash (e.g., `'fr/'`, `''`)
   - `localePrefix`: The locale identifier without slashes (e.g., `'fr'`, `undefined`)
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -173,15 +167,11 @@ console.log(`Current locale: ${localePrefix}`);
 // Output: "Current locale: fr"
 ```
 
----
-
 ## Related Functions
 
 - [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md): Generates a localized URL for a specific locale
 - [`getMultilingualUrls`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getMultilingualUrls.md): Generates URLs for all configured locales
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en/packages/next-intlayer/t.md

@@ -32,14 +32,10 @@ author: aymericzip
 
 The `t` function in the `next-intlayer` package is a fundamental tool for inline internationalization within your Next.js application. It allows you to define translations directly within your components, making it simple to display localized content based on the current locale.
 
----
-
 ## Overview
 
 The `t` function is used to provide translations for different locales directly in your components. By passing an object containing translations for each supported locale, `t` returns the appropriate translation based on the current locale context in your Next.js application.
 
----
-
 ## Key Features
 
 - **Inline Translations**: Ideal for quick, inline text that doesn't require a separate content declaration.
@@ -47,8 +43,6 @@ The `t` function is used to provide translations for different locales directly
 - **TypeScript Support**: Provides type safety and autocompletion when used with TypeScript.
 - **Easy Integration**: Works seamlessly within both client and server components in Next.js.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -63,8 +57,6 @@ t<T extends string>(content: Record<LocalesValues, T>, locale?: Locales): string
 
 - A string representing the translated content for the current locale.
 
----
-
 ## Usage Examples
 
 ### Using `t` in a Client Component
@@ -134,8 +126,6 @@ When localizing attributes like `alt`, `title`, `href`, or `aria-label`, you can
 </button>
 ```
 
----
-
 ## Advanced Topics
 
 ### TypeScript Integration
@@ -197,8 +187,6 @@ const Page: FC<{ locale: Locales; children: ReactNode }> = ({
  </Tab>
 </Tabs>
 
----
-
 ## Common Errors and Troubleshooting
 
 ### `t` Returns Undefined or Incorrect Translation
@@ -223,8 +211,6 @@ const translations: IConfigLocales<string> = {
 const text = t(translations);
 ```
 
----
-
 ## Tips for Effective Usage
 
 1. **Use `t` for Simple Inline Translations**: Ideal for translating small pieces of text directly within your components.
@@ -232,14 +218,10 @@ const text = t(translations);
 3. **Consistent Locale Provision**: Ensure that your locale is consistently provided across your application through the appropriate providers.
 4. **Leverage TypeScript**: Use TypeScript types to catch missing translations and ensure type safety.
 
----
-
 ## Conclusion
 
 The `t` function in `next-intlayer` is a powerful and convenient tool for managing inline translations in your Next.js applications. By integrating it effectively, you enhance the internationalization capabilities of your app, providing a better experience for users worldwide.
 
 For more detailed usage and advanced features, refer to the [next-intlayer documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md).
 
----
-
 **Note**: Remember to set up your `IntlayerProvider` (or `IntlayerClientProvider` and `IntlayerServerProvider`) properly to ensure that the current locale is correctly passed down to your components. This is crucial for the `t` function to return the correct translations.

package/docs/en/packages/react-intlayer/t.md

@@ -28,14 +28,10 @@ author: aymericzip
 
 The `t` function in the `react-intlayer` package is a fundamental tool for inline internationalization within your React application. It allows you to define translations directly within your components, making it simple to display localized content based on the current locale.
 
----
-
 ## Overview
 
 The `t` function is used to provide translations for different locales directly in your components. By passing an object containing translations for each supported locale, `t` returns the appropriate translation based on the current locale context in your React application.
 
----
-
 ## Key Features
 
 - **Inline Translations**: Ideal for quick, inline text that doesn't require a separate content declaration.
@@ -43,8 +39,6 @@ The `t` function is used to provide translations for different locales directly
 - **TypeScript Support**: Provides type safety and autocompletion when used with TypeScript.
 - **Easy Integration**: Works seamlessly within React components.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -59,8 +53,6 @@ t<T extends string>(content: Record<LocalesValues, T>, locale?: Locales): string
 
 - A string representing the translated content for the current locale.
 
----
-
 ## Usage Examples
 
 ### Basic Usage of `t` in a Component
@@ -112,8 +104,6 @@ The `t` function is particularly useful for inline translations in JSX attribute
 </button>
 ```
 
----
-
 ## Advanced Topics
 
 ### TypeScript Integration
@@ -150,8 +140,6 @@ const App: FC<{ locale: Locales }> = ({ locale }) => (
 );
 ```
 
----
-
 ## Common Errors and Troubleshooting
 
 ### `t` Returns Undefined or Incorrect Translation
@@ -176,8 +164,6 @@ const translations: IConfigLocales<string> = {
 const text = t(translations);
 ```
 
----
-
 ## Tips for Effective Usage
 
 1. **Use `t` for Simple Inline Translations**: Ideal for translating small pieces of text directly within your components.
@@ -185,14 +171,10 @@ const text = t(translations);
 3. **Consistent Locale Provision**: Ensure that your locale is consistently provided across your application through the `IntlayerProvider`.
 4. **Leverage TypeScript**: Use TypeScript types to catch missing translations and ensure type safety.
 
----
-
 ## Conclusion
 
 The `t` function in `react-intlayer` is a powerful and convenient tool for managing inline translations in your React applications. By integrating it effectively, you enhance the internationalization capabilities of your app, providing a better experience for users worldwide.
 
 For more detailed usage and advanced features, refer to the [react-intlayer documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md).
 
----
-
 **Note**: Remember to set up your `IntlayerProvider` properly to ensure that the current locale is correctly passed down to your components. This is crucial for the `t` function to return the correct translations.

package/docs/en/readme.md

@@ -68,8 +68,6 @@ With **per-locale content files**, **TypeScript autocompletion**, **tree-shakabl
 | <img src="https://github.com/aymericzip/intlayer/blob/main/docs/assets/interoperability.png?raw=true" alt="Feature" width="700">                    | **Interoperability**<br><br>Allow interoperability with react-i18next, next-i18next, next-intl, react-intl, vue-i18n. <br><br> - [Intlayer and react-intl](https://intlayer.org/blog/intlayer-with-react-intl) <br> - [Intlayer and next-intl](https://intlayer.org/blog/intlayer-with-next-intl) <br> - [Intlayer and next-i18next](https://intlayer.org/blog/intlayer-with-next-i18next) <br> - [Intlayer and vue-i18n](https://intlayer.org/blog/intlayer-with-vue-i18n) <br> - [Intlayer compat adapters](https://intlayer.org/doc/compatibility) |
 | <img src="https://github.com/aymericzip/intlayer/blob/main/docs/assets/benchmark.png?raw=true" alt="Feature" width="700">                           | **Performances & Benchmark**<br><br>Uses advanced tree-shaking and dynamic loading to boost performances and keep the solution as light as possible. <br><br> - [Performances & Benchmark](https://intlayer.org/doc/benchmark)                                                                                                                                                                                                                                                                                                                        |
 
----
-
 ## 📦 Installation
 
 Start your journey with Intlayer today and experience a smoother, more powerful approach to internationalization.
@@ -195,12 +193,9 @@ Explore our comprehensive documentation to get started with Intlayer and learn h
       <li><a href="https://intlayer.org/doc/environment/nextjs/15" rel=''>Next.js 15</a></li>
       <li><a href="https://intlayer.org/doc/environment/nextjs/14" rel=''>Next.js 14 (App Router)</a></li>
       <li><a href="https://intlayer.org/doc/environment/nextjs/next-with-page-router" rel=''>Next.js Page Router</a></li>
-      <li><a href="https://intlayer.org/doc/environment/nextjs/compiler" rel=''>Next.js using Compiler</a></li>
     </ul>
   </li>
-  <li><a href="https://intlayer.org/doc/environment/create-react-app" rel=''>React CRA</a></li>
   <li><a href="https://intlayer.org/doc/environment/vite-and-react" rel=''>Vite + React</a></li>
-  <li><a href="https://intlayer.org/doc/environment/vite-and-react" rel=''>Vite + React using Compiler</a></li>
   <li><a href="https://intlayer.org/doc/environment/vite-and-react/compiler" rel=''>React-router-v7</a></li>
   <li><a href="https://intlayer.org/doc/environment/tanstack-start" rel=''>Tanstack start</a>
     <ul>

package/docs/en/releases/v6.md

@@ -42,8 +42,6 @@ Welcome to Intlayer v6! This release focuses on performance, developer experienc
 - Live updates with CMS using `build.importMode = 'live'` and `pnpm intlayer live`
 - Fixes: Vue.js integration, Lynx adapter, Visual Editor on Windows
 
----
-
 ## New: Test missing translations
 
 Quickly audit your project to find which keys/locales are missing.
@@ -82,8 +80,6 @@ Total missing required locales: 0
 
 See more options in the CLI docs: [CLI reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md) → "Test missing translations". As well as the [Testing](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/testing.md) guide.
 
----
-
 ## New: Global autoFill to complete missing translations
 
 You can now enable auto‑fill globally so any dictionary with missing translations gets completed automatically.
@@ -120,8 +116,6 @@ Auto-fill your missing translations using the `npx intlayer fill` command.
 
 You can still fine‑tune per dictionary using the `autoFill` field in content files. Intlayer will first consider the per dictionary configuration and then fallback to the global configuration. See the full reference in [Auto-fill](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/autoFill.md) and [Content file reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/content_file.md).
 
----
-
 ## Fill command: safer defaults
 
 The fill command now, by default, only fills missing translations and skips existing content.
@@ -159,8 +153,6 @@ Affected dictionary keys for processing: access-key-creation-form-schema, doc-se
 
 CI examples are available in [CI/CD](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/CI_CD.md).
 
----
-
 ## Updated VS Code extension
 
 The extension now includes a dedicated Intlayer tab in the Activity Bar and several workflow improvements:
@@ -175,8 +167,6 @@ The extension now includes a dedicated Intlayer tab in the Activity Bar and seve
 
 See details in the [Official VS Code Extension](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/vs_code_extension.md) documentation.
 
----
-
 Updated the MCP server to support the new features.
 
 - Auto-fill
@@ -189,8 +179,6 @@ Updated the MCP server to support the new features.
 
 > MCP server helps for the automatisation of project using Intlayer. Testing missing translations for autogenerated code. It helps understanding your config, and embed the documentation of Intlayer in your IDE.
 
----
-
 ## Performance: 10× faster
 
 - Parallel resolution of local and remote dictionaries
@@ -233,8 +221,6 @@ Output:
 [intlayer]  Content loaded  (Total: 8401ms - Local: 4050ms - Remote: 4222ms)
 ```
 
----
-
 ## Logging improvements
 
 The logging system has been improved to provide more detailed information about what happens during build and runtime transformations.
@@ -251,14 +237,10 @@ export default {
 
 See [Configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md) for all logging options.
 
----
-
 ## Stronger validation
 
 Dictionary processing now performs more robust validation. When a dictionary fails to process, Intlayer avoids breaking your application and surfaces actionable errors.
 
----
-
 ## Live updates with CMS (Production‑safe)
 
 Serve live content updates (e.g., editorial updates) in production without rebuilding your application.
@@ -321,8 +303,6 @@ To work around this, we dropped the `intlayer watch` command, using the `--with`
 }
 ```
 
----
-
 ## Migration notes
 
 - Removed: `dictionaryOutput` (previously `i18next` or `next-intl`). This will come back as pluggable adapters in future versions. Remove the field from your config.
@@ -332,22 +312,16 @@ To work around this, we dropped the `intlayer watch` command, using the `--with`
 - For verbose diagnostics, set `log.mode = 'verbose'`.
 - Use `intlayer` instead of `intlayerPlugin` and `intlayerProxy` instead of `intlayerProxyPlugin` in your Vite configuration.
 
----
-
 ## Fixes
 
 - Vue.js integration stability
 - Lynx adapter improvements
 - Visual Editor on Windows
 
----
-
 ## Migration notes from v6 to v7
 
 Check the [migration notes from v6 to v7](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v7.md) for more information.
 
----
-
 ## Useful links
 
 - [CLI reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md)