@intlayer/docs 8.12.4-canary.0 → 8.12.5-canary.0

package/blog/en/list_i18n_technologies/frameworks/react.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - react
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your React Website

package/blog/en/list_i18n_technologies/frameworks/svelte.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - svelte
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your Svelte Website

package/blog/en/list_i18n_technologies/frameworks/vue.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - vue
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your Vue.js Website

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

@@ -15,6 +15,7 @@ keywords:
 slugs:
   - blog
   - next-i18next-vs-next-intl-vs-intlayer
+author: aymericzip
 ---
 
 # next-i18next VS next-intl VS intlayer | Next.js Internationalization (i18n)

package/blog/en/nextjs-multilingual-seo-comparison.md

@@ -16,6 +16,7 @@ keywords:
 slugs:
   - blog
   - blog-seo-i18n-nextjs
+author: aymericzip
 ---
 
 # SEO and i18n in Next.js: Translating is not enough

package/blog/en/per-component_vs_centralized_i18n.md

@@ -13,6 +13,7 @@ keywords:
 slugs:
   - blog
   - per-component-vs-centralized-i18n
+author: aymericzip
 ---
 
 # Per-Component vs. Centralized i18n

package/blog/en/rag_powered_documentation_assistant.md

@@ -13,6 +13,7 @@ keywords:
 slugs:
   - blog
   - rag-powered-documentation-assistant
+author: aymericzip
 ---
 
 # Building a RAG-Powered Documentation Assistant (Chunking, Embeddings, and Search)
@@ -69,13 +70,17 @@ At a high level, here’s the recipe I used:
 5.  **Augmentation + Generation (AG in RAG)** Those chunks are injected into the prompt for ChatGPT, so the model answers with actual doc context.
 6.  **Logging queries for feedback** Every user query is stored. This is gold for understanding pain points, missing docs, or new opportunities.
 
-## Step 1: Reading the Docs
+<Steps>
+
+<Step number={1} title="Reading the Docs">
 
 The first step was simple: I needed a way to scan a docs/ folder for all .md files. Using Node.js and glob, I fetched the content of each Markdown file into memory.
 
 This keeps the pipeline flexible: instead of Markdown, you could fetch docs from a database, a CMS, or even an API.
 
-## Step 2: Chunking the Documentation
+</Step>
+
+<Step number={2} title="Chunking the Documentation">
 
 Why chunk? Because language models have **context limits**. Feeding them an entire book of docs won’t work.
 
@@ -97,7 +102,9 @@ This trade-off (chunk size vs overlap) is key for RAG efficiency:
 - Too small → you get noise.
 - Too large → you blow up context size.
 
-## Step 3: Generating Embeddings
+</Step>
+
+<Step number={3} title="Generating Embeddings">
 
 Once the docs are chunked, we generate **embeddings**, high-dimensional vectors representing each chunk.
 
@@ -115,7 +122,9 @@ I used OpenAI’s text-embedding-3-large model, but you could use any modern e
 
 Each vector is a mathematical fingerprint of the text, enabling similarity search.
 
-## Step 4: Indexing & Storing Embeddings
+</Step>
+
+<Step number={4} title="Indexing & Storing Embeddings">
 
 To avoid regenerating embeddings multiple times, I stored them in embeddings.json.
 
@@ -128,7 +137,9 @@ In production, you’d likely want a vector database such as:
 
 Vector DBs handle indexing, scalability, and fast search. But for my prototype, a local JSON worked fine.
 
-## Step 5: Retrieval with Cosine Similarity
+</Step>
+
+<Step number={5} title="Retrieval with Cosine Similarity">
 
 When a user asks a question:
 
@@ -140,7 +151,9 @@ Cosine similarity measures the angle between two vectors. A perfect match scores
 
 This way, the system finds the closest doc passages to the query.
 
-## Step 6: Augmentation + Generation
+</Step>
+
+<Step number={6} title="Augmentation + Generation">
 
 Now comes the magic. We take the top chunks and inject them into the **system prompt** for ChatGPT.
 
@@ -148,7 +161,9 @@ That means the model answers as if those chunks were part of the conversation.
 
 The result: accurate, **doc-grounded responses**.
 
-## Step 7: Logging User Queries
+</Step>
+
+<Step number={7} title="Logging User Queries">
 
 This is the hidden superpower.
 
@@ -161,7 +176,9 @@ Every question asked is stored. Over time, you build a dataset of:
 
 This turns your RAG assistant into a **continuous user research tool**.
 
-## What Does It Cost?
+</Step>
+
+<Step number={8} title="What Does It Cost?">
 
 One common objection to RAG is cost. In practice, it’s surprisingly cheap:
 
@@ -171,7 +188,9 @@ One common objection to RAG is cost. In practice, it’s surprisingly cheap:
 
 On the top of that, you can include the hosting cost.
 
-## Implementation Details
+</Step>
+
+<Step number={9} title="Implementation Details">
 
 Stack:
 
@@ -235,7 +254,9 @@ We experimented with gpt-5, but latency was too high (sometimes up to 15 second
 
 👉 [Try the demo here](https://intlayer.org/doc/why) 👉 [Check the code template on GitHub](https://github.com/aymericzip/smart_doc_RAG)
 
-## Going Further
+</Step>
+
+<Step number={10} title="Going Further">
 
 This project is a minimal implementation. But you can extend it in many ways:
 
@@ -247,13 +268,17 @@ This project is a minimal implementation. But you can extend it in many ways:
 - Multi-source retrieval → pull not just docs, but database entries, blog posts, tickets, etc.
 - Improved prompting → reranking, filtering, and hybrid search (keyword + semantic)
 
-## Limitations We Hit
+</Step>
+
+<Step number={11} title="Limitations We Hit">
 
 - Chunking and overlap are empirical. The right balance (chunk size, overlap percentage, number of retrieved chunks) requires iteration and testing.
 - Embeddings are not auto-regenerated when docs change. Our system resets embeddings for a file only if the number of chunks differs from what’s stored.
 - In this prototype, embeddings are stored in JSON. This works for demos but pollutes Git. In production, a database or dedicated vector store is better.
 
-## Why This Matters Beyond Docs
+</Step>
+
+<Step number={12} title="Why This Matters Beyond Docs">
 
 The interesting part is not just the chatbot. It’s the **feedback loop**.
 
@@ -273,6 +298,10 @@ Imagine launching a new feature and instantly seeing:
 
 That’s **product intelligence** straight from your users.
 
+</Step>
+
+</Steps>
+
 ## Conclusion
 
 RAG is one of the simplest, most powerful ways to make LLMs practical. By combining **retrieval + generation**, you can turn static docs into a **smart assistant** and, at the same time, gain a continuous stream of product insights.

package/blog/en/react-i18next_vs_react-intl_vs_intlayer.md

@@ -15,6 +15,7 @@ keywords:
 slugs:
   - blog
   - react-i18next-vs-react-intl-vs-intlayer
+author: aymericzip
 ---
 
 # react-Intl VS react-i18next VS intlayer | React Internationalization (i18n)

package/blog/en/vue-i18n_vs_intlayer.md

@@ -15,6 +15,7 @@ keywords:
 slugs:
   - blog
   - vue-i18n-vs-intlayer
+author: aymericzip
 ---
 
 # vue-i18n VS Intlayer | Vue Internationalization (i18n)

package/blog/en/what_is_internationalization.md

@@ -15,6 +15,7 @@ keywords:
 slugs:
   - blog
   - what-is-internationalization
+author: aymericzip
 ---
 
 # What is Internationalization (i18n)? Definition and challenges

package/blog/en-GB/compiler_vs_declarative_i18n.md

@@ -16,6 +16,7 @@ keywords:
 slugs:
   - blog
   - compiler-vs-declarative-i18n
+author: aymericzip
 ---
 
 # The Case for and Against Compiler-Based i18n

package/blog/en-GB/i18n_meaning.md

@@ -14,6 +14,7 @@ keywords:
 slugs:
   - blog
   - i18n-meaning
+author: aymericzip
 ---
 
 # i18n Meaning: What is Internationalisation and why is it important?

package/blog/en-GB/i18n_using_next-i18next.md

@@ -19,6 +19,7 @@ history:
   - version: 7.0.6
     date: 2025-11-01
     changes: Initial version
+author: aymericzip
 ---
 
 # How to internationalise your Next.js application using next-i18next in 2026

package/blog/en-GB/i18n_using_next-intl.md

@@ -18,6 +18,7 @@ history:
   - version: 7.0.0
     date: 2025-11-01
     changes: Initial version
+author: aymericzip
 ---
 
 # How to internationalise your Next.js application using next-intl in 2026

package/blog/en-GB/index.md

@@ -13,6 +13,7 @@ keywords:
 slugs:
   - blog
   - search
+author: aymericzip
 ---
 
 # Embracing Internationalization in JavaScript: Enhancing Global Reach and SEO

package/blog/en-GB/internationalization_and_SEO.md

@@ -14,6 +14,7 @@ keywords:
 slugs:
   - blog
   - SEO-and-i18n
+author: aymericzip
 ---
 
 # SEO & I18n: The Ultimate Guide to Making Your Website Multilingual

package/blog/en-GB/intlayer_with_i18next.md

@@ -27,6 +27,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin
+author: aymericzip
 ---
 
 # How to automate your i18next JSON translations using Intlayer
@@ -67,7 +68,9 @@ This guide explains how to leverage Intlayer as an **adapter for i18next**, allo
 
 ## Step-by-Step Guide to Set Up Intlayer with i18next
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages:
 
@@ -96,7 +99,9 @@ bun x intlayer init
 - **intlayer**: Core library for internationalisation management, content declaration, and building
 - **@intlayer/sync-json-plugin**: Plugin to export Intlayer content declarations to i18next compatible JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -132,6 +137,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 To see more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 It is recommended to ignore auto-generated Intlayer files:

package/blog/en-GB/intlayer_with_next-i18next.md

@@ -23,6 +23,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin and comprehensive rewrite
+author: aymericzip
 ---
 
 # Next.js Internationalisation (i18n) with next-i18next and Intlayer
@@ -76,7 +77,9 @@ This guide explains how to leverage Intlayer as an **adapter for i18next**, allo
 
 ## Step-by-Step Guide to Set Up Intlayer with next-i18next
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages using your preferred package manager:
 
@@ -105,7 +108,9 @@ bun x intlayer init
 - **intlayer**: Core library for content declaration and management
 - **@intlayer/sync-json-plugin**: Plugin to synchronise Intlayer content declarations to i18next JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -141,6 +146,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 To see more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 Exclude generated files from version control:

package/blog/en-GB/intlayer_with_next-intl.md

@@ -22,6 +22,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin
+author: aymericzip
 ---
 
 # How to automate your next-intl JSON translations using Intlayer
@@ -62,7 +63,9 @@ This guide explains how to leverage Intlayer as an **adapter for next-intl**, al
 
 ## Step-by-Step Guide to Set Up Intlayer with next-intl
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages:
 
@@ -91,7 +94,9 @@ bun x intlayer init
 - **intlayer**: Core library for internationalisation management, content declaration, and building
 - **@intlayer/sync-json-plugin**: Plugin to export Intlayer content declarations to next-intl compatible JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -129,6 +134,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 For more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 It is recommended to ignore auto-generated Intlayer files:

package/blog/en-GB/intlayer_with_react-i18next.md

@@ -25,6 +25,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin
+author: aymericzip
 ---
 
 # How to automate your react-i18next JSON translations using Intlayer
@@ -65,7 +66,9 @@ This guide explains how to leverage Intlayer as an **adapter for react-i18next**
 
 ## Step-by-Step Guide to Set Up Intlayer with react-i18next
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages:
 
@@ -94,7 +97,9 @@ bun x intlayer init
 - **intlayer**: Core library for internationalisation management, content declaration, and building
 - **@intlayer/sync-json-plugin**: Plugin to export Intlayer content declarations to react-i18next compatible JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -130,6 +135,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 To see more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 It is recommended to ignore auto-generated Intlayer files:

package/blog/en-GB/intlayer_with_react-intl.md

@@ -23,6 +23,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin
+author: aymericzip
 ---
 
 # How to automate your react-intl JSON translations using Intlayer
@@ -63,7 +64,9 @@ This guide explains how to leverage Intlayer as an **adapter for react-intl**, a
 
 ## Step-by-Step Guide to Set Up Intlayer with react-intl
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages:
 
@@ -92,7 +95,9 @@ bun x intlayer init
 - **intlayer**: Core library for internationalisation management, content declaration, and building
 - **@intlayer/sync-json-plugin**: Plugin to export Intlayer content declarations to react-intl compatible JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -129,6 +134,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 To see more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 It is recommended to ignore auto-generated Intlayer files:

package/blog/en-GB/intlayer_with_vue-i18n.md

@@ -23,6 +23,7 @@ history:
   - version: 7.0.0
     date: 2025-10-29
     changes: Change to syncJSON plugin and comprehensive rewrite
+author: aymericzip
 ---
 
 # Vue.js Internationalisation (i18n) with vue-i18n and Intlayer
@@ -65,7 +66,9 @@ This guide explains how to leverage Intlayer as an **adapter for vue-i18n**, all
 
 ## Step-by-Step Guide to Set Up Intlayer with vue-i18n
 
-### Step 1: Install Dependencies
+<Steps>
+
+<Step number={1} title="Install Dependencies">
 
 Install the necessary packages using your preferred package manager:
 
@@ -94,7 +97,9 @@ bun x intlayer init
 - **intlayer**: Core library for content declaration and management
 - **@intlayer/sync-json-plugin**: Plugin to synchronise Intlayer content declarations to vue-i18n JSON format
 
-### Step 2: Implement the Intlayer plugin to wrap the JSON
+</Step>
+
+<Step number={2} title="Implement the Intlayer plugin to wrap the JSON">
 
 Create an Intlayer configuration file to define your supported locales:
 
@@ -131,6 +136,10 @@ If changes are made using the CLI to translate the JSON, or using the CMS, Intla
 
 To see more details about the `syncJSON` plugin, please refer to the [syncJSON plugin documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/plugins/sync-json.md).
 
+</Step>
+
+</Steps>
+
 ## Git Configuration
 
 Exclude generated files from version control:

package/blog/en-GB/l10n_platform_alternative/Lokalise.md

@@ -15,6 +15,7 @@ history:
   - version: 7.5.0
     date: 2025-12-18
     changes: Initial version
+author: aymericzip
 ---
 
 # An open-source L10n alternative to Lokalise (TMS)

package/blog/en-GB/l10n_platform_alternative/crowdin.md

@@ -15,6 +15,7 @@ history:
   - version: 7.5.0
     date: 2025-12-18
     changes: Initial version
+author: aymericzip
 ---
 
 # An open-source L10n alternative to Crowdin (TMS)

package/blog/en-GB/l10n_platform_alternative/phrase.md

@@ -15,6 +15,7 @@ history:
   - version: 7.5.0
     date: 2025-12-18
     changes: Initial version
+author: aymericzip
 ---
 
 # An L10n open-source alternative to Phrase (TMS)

package/blog/en-GB/list_i18n_technologies/frameworks/angular.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - angular
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your Angular Website

package/blog/en-GB/list_i18n_technologies/frameworks/react-native.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - react-native
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your React Native App

package/blog/en-GB/list_i18n_technologies/frameworks/react.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - react
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your React Website

package/blog/en-GB/list_i18n_technologies/frameworks/svelte.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - svelte
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your Svelte Website

package/blog/en-GB/list_i18n_technologies/frameworks/vue.md

@@ -16,6 +16,7 @@ slugs:
   - i18n-technologies
   - frameworks
   - vue
+author: aymericzip
 ---
 
 # Exploring i18n Solutions to Translate Your Vue.js Website

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

@@ -15,6 +15,7 @@ keywords:
 slugs:
   - blog
   - next-i18next-vs-next-intl-vs-intlayer
+author: aymericzip
 ---
 
 # next-i18next VS next-intl VS intlayer | Next.js Internationalisation (i18n)

package/blog/en-GB/nextjs-multilingual-seo-comparison.md

@@ -16,6 +16,7 @@ keywords:
 slugs:
   - blog
   - blog-seo-i18n-nextjs
+author: aymericzip
 ---
 
 # SEO and i18n in Next.js: Translating is not enough

package/blog/en-GB/per-component_vs_centralized_i18n.md

@@ -13,6 +13,7 @@ keywords:
 slugs:
   - blog
   - per-component-vs-centralized-i18n
+author: aymericzip
 ---
 
 # Per-Component vs. Centralized i18n