@intlayer/docs 9.4.4 → 9.5.0

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

@@ -29,14 +29,10 @@ author: aymericzip
 
 The `t` function in the `next-intlayer` package is a fundamental tool for inline internationalisation within your Next.js application. It allows you to define translations directly within your components, making it simple to display localised 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.
@@ -44,8 +40,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
@@ -60,8 +54,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 localising attributes like `alt`, `title`, `href`, or `aria-label`, you can
 </button>
 ```
 
----
-
 ## Advanced Topics
 
 ### TypeScript Integration
@@ -197,8 +187,6 @@ const Page: FC<{ locale: Locales }> = ({ locale }) => (
  </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 internationalisation 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-GB/intlayer_visual_editor.md).
 
----
-
 **Note**: Remember to set up your `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-GB/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 internationalisation within your React application. It allows you to define translations directly within your components, making it simple to display localised 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 especially useful for inline translations within JSX attribu
 </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 internationalisation 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-GB/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-GB/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>Enables 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 internationalisation.

package/docs/en-GB/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-GB/cli/index.md) → "Test missing translations". As well as the [Testing](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/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. See the full reference in `doc/autoFill` and `doc/dictionary/content_file`.
 
----
-
 ## 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-GB/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-GB/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 with the automation of projects using Intlayer. Testing missing translations for autogenerated code. It helps understand your config, and embed the documentation of Intlayer in your IDE.
 
----
-
 ## Performance: 10× faster
 
 - Parallel resolution of local and remote dictionaries
@@ -240,8 +228,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.
@@ -258,26 +244,29 @@ export default {
 
 See [Configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/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)
 
-The logging system has been improved to provide more detailed information about what happens during build and runtime transformations.
+Serve live content updates (e.g., editorial updates) in production without rebuilding your application.
 
-> Enable verbose logs to better understand what happens during build and runtime transformations.
+1. Enable live import mode:
 
 ```ts fileName="intlayer.config.ts"
-export default {
-  log: {
-    mode: "verbose", // options: "default" | "verbose" | "disabled"
+import { type IntlayerConfig } from "intlayer";
+
+const config: IntlayerConfig = {
+  build: {
+    importMode: "live", // "static" | "dynamic" | "live"
+  },
+  editor: {
+    liveSync: true, // enable live sync server side
   },
 };
+
+export default config;
 ```
 
 2. Run your app and live process side‑by‑side:
@@ -300,24 +289,27 @@ bun x intlayer live --with 'vite preview'
 
 Notes:
 
-See [Configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/configuration.md) for all logging options.
+- Only dictionaries flagged to use live mode will be fetched live. Others are optimized for performance.
+- Falls back to dynamic import if the live API isn’t reachable.
 
----
+See [CMS and Live Sync](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md) and [Configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/configuration.md) for complete guidance.
 
-## Live updates with CMS (Production‑safe)
+## Parallel process to watch files on turbopack
 
-Serve live content updates (e.g., editorial updates) in production without rebuilding your application.
+When using Turbopack on Next.js 14 and above as your development server with the `next dev --turbopack` command, dictionary changes will not be automatically detected by default.
 
-1. Enable live import mode:
+This limitation occurs because Turbopack cannot run webpack plugins in parallel to monitor changes in your content files.
 
-2. Run your app and live process side‑by‑side:
+To work around this, we dropped the `intlayer watch` command, using the `--with` option to run both the development server and the Intlayer build watcher simultaneously.
 
-```bash packageManager="bun"
-bun x intlayer live --with 'vite preview'
+```json5 fileName="package.json"
+{
+  "scripts": {
+    "dev": "npx intlayer watch --with 'next dev --turbopack'",
+  },
+}
 ```
 
----
-
 ## Migration notes
 
 - Removed: `dictionaryOutput` (previously `i18next` or `next-intl`). This will return as pluggable adapters in future versions. Remove the field from your config.
@@ -326,22 +318,16 @@ bun x intlayer live --with 'vite preview'
 - Use `npx intlayer content test` to gate PRs on missing translations.
 - For verbose diagnostics, set `log.mode = 'verbose'`.
 
----
-
 ## 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-GB/cli/index.md)

package/docs/en-GB/releases/v7.md

@@ -45,8 +45,6 @@ Welcome to Intlayer v7! This major release introduces significant improvements i
 - Parallelisation for faster translation processing
 - Smart chunking to handle large files within AI context limits
 
----
-
 ## 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.
@@ -73,8 +71,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.
@@ -99,8 +95,6 @@ Benefits:
 - Better type safety with no cross-locale type pollution
 - Improved performance by reducing type complexity
 
----
-
 ## Bundle optimisation: Locales as strings
 
 The `Locales` type is no longer an enum, which means it is now fully tree-shakeable and will not bloat your bundle with thousands of unused locale records.
@@ -127,8 +121,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.
@@ -159,8 +151,6 @@ export default {
 };
 ```
 
----
-
 ## GDPR compliance: localStorage / cookies storage
 
 v7 prioritises 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.
@@ -250,8 +240,6 @@ setLocale("en");
 **Note:** Cookies are 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 optimised to be 30% smaller than the previous version, thanks to:
@@ -262,8 +250,6 @@ The Visual Editor package has been optimised 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.
@@ -321,8 +307,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 organisation for dictionary-related settings and improved content management.
@@ -382,8 +366,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-GB/dictionary/content_file.md).
 
----
-
 ## Fill command: Updated behaviour for better content management
 
 v7 introduces improved behaviour for the `fill` command, providing more predictable and flexible content management:
@@ -469,8 +451,6 @@ const content = {
 };
 ```
 
----
-
 ## Enhanced stability and translation management
 
 v7 introduces several improvements to make content translation more reliable and efficient:
@@ -520,8 +500,6 @@ The system automatically:
 4. Validates and retries if needed
 5. Reconstructs the complete file
 
----
-
 ## Migration notes from v6
 
 ### Removed configurations
@@ -610,14 +588,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-GB/releases/v6.md) for more information.
 
----
-
 ## Useful links
 
 - [Configuration Reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/configuration.md)

package/docs/en-GB/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-GB/dictionary/html.md) and [Markdown Documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/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-GB/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.
@@ -817,8 +809,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.
@@ -861,8 +851,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 localised content directly as if it were a standard string, number, boolean, or array primitive.
@@ -889,8 +877,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()`.
@@ -964,8 +950,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.
@@ -1084,8 +1068,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 internationalisation workflow:
@@ -1094,8 +1076,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:
@@ -1105,15 +1085,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,
@@ -1135,7 +1113,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";
@@ -1160,8 +1138,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 optimise your production bundle:
@@ -1202,8 +1178,6 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
----
-
 ## Flexibility: Unified Import Mode
 
 The `live` boolean property has been deprecated in favour of a more comprehensive `importMode` property. This allows for explicit definition of how dictionaries should be loaded: statically, dynamically, or via live sync.
@@ -1244,8 +1218,6 @@ export default {
 }
 ```
 
----
-
 ## Dictionary Location Control
 
 v8 introduces the `location` property to explicitly manage where dictionaries live and how they synchronise. This is particularly useful for hybrid workflows involving both local files and remote CMS content.
@@ -1266,8 +1238,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.
@@ -1307,8 +1277,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.
@@ -1343,22 +1311,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 optimisation in router architectures like TanStack Router:
@@ -1392,8 +1354,6 @@ export const Route = createFileRoute("/sitemap.xml")({
 });
 ```
 
----
-
 ## Migration notes from v7
 
 ### Configuration Changes
@@ -1403,8 +1363,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-GB/configuration.md)