@intlayer/docs 9.3.3 → 9.4.0

package/README.md

@@ -214,6 +214,7 @@ Explore our comprehensive documentation to get started with Intlayer and learn h
   <li><a href="https://intlayer.org/doc/environment/vite-and-vue" rel=''>Vite + Vue</a></li>
   <li><a href="https://intlayer.org/doc/environment/nuxt-and-vue" rel=''>Vite + Nuxt</a></li>
   <li><a href="https://intlayer.org/doc/environment/vite-and-solid" rel=''>Vite + Solid</a></li>
+  <li><a href="https://intlayer.org/doc/environment/solid-start" rel=''>Solid Start</a></li>
   <li><a href="https://intlayer.org/doc/environment/angular" rel=''>Angular</a></li>
   <li>
      <a href="https://intlayer.org/doc/environment/express" rel=''>Backend</a>
@@ -223,7 +224,9 @@ Explore our comprehensive documentation to get started with Intlayer and learn h
       <li><a href="https://intlayer.org/doc/environment/fastify" rel=''>Fastify</a></li>
       <li><a href="https://intlayer.org/doc/environment/adonisjs" rel=''>AdonisJS</a></li>
       <li><a href="https://intlayer.org/doc/environment/hono" rel=''>Hono</a></li>
+      <li><a href="https://intlayer.org/doc/environment/elysia" rel=''>Elysia</a></li>
     </ul>
+
   </li>
 </ul>
 </details>
@@ -327,4 +330,4 @@ Contribute on [GitHub](https://github.com/aymericzip/intlayer), [GitLab](https:/
 
 If you like Intlayer, give us a ⭐ on GitHub. It helps others discover the project! [See why GitHub Stars matter](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md#why-github-stars-matter-).
 
-[![Star History Chart](https://api.star-history.com/svg?repos=aymericzip/intlayer&type=Date)](https://star-history.com/#aymericzip/intlayer&Date)
+[![Star History Chart](https://star-history.dera.page/svg?repos=aymericzip/intlayer&type=Date)](https://star-history.dera.page/#aymericzip/intlayer&Date)

package/authors.json

@@ -3,7 +3,7 @@
     "name": "Aymeric PINEAU",
     "title": "Founder of Intlayer, open-source multilingual CMS for Next.js and React",
     "url": "https://github.com/aymericzip",
-    "image": "https://avatars.githubusercontent.com/u/62554073?v=4&size=124",
+    "image": "https://intlayer.org/assets/authors/aymericzip.webp",
     "socialMedias": [
       "https://www.linkedin.com/in/aymericpineau/",
       "https://x.com/aymericzip",

package/blog/ar/i18n_using_next-i18next.md

@@ -453,6 +453,9 @@ export default function LocaleLayout({
 
 تنظيم الترجمات حسب مساحة الاسم (مثل `common.json`، `about.json`) يتيح تقسيم الكود ويقلل من حجم الحزمة. تقوم بتحميل الترجمات اللازمة فقط لكل صفحة، مما يحسن الأداء.
 
+<Tabs group="locale">
+ <Tab value='en' label='الإنجليزية'>
+
 ```json fileName="src/locales/en/common.json"
 {
   "appTitle": "Next.js i18n App",
@@ -460,6 +463,9 @@ export default function LocaleLayout({
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='الفرنسية'>
+
 ```json fileName="src/locales/fr/common.json"
 {
   "appTitle": "Application Next.js i18n",
@@ -467,6 +473,12 @@ export default function LocaleLayout({
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='الإنجليزية'>
+
 ```json fileName="src/locales/en/home.json"
 {
   "title": "Home",
@@ -478,29 +490,56 @@ export default function LocaleLayout({
 }
 ```
 
-```json fileName="src/locales/ar/home.json"
+ </Tab>
+ <Tab value='fr' label='الفرنسية'>
+
+```json fileName="src/locales/fr/home.json"
+{
+  "title": "Accueil",
+  "description": "Description de la page d'accueil",
+  "welcome": "Bienvenue",
+  "greeting": "Bonjour le monde!",
+  "aboutPage": "Page À propos",
+  "documentation": "Documentation"
+}
+```
+
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='الإنجليزية'>
+
+```json fileName="src/locales/en/about.json"
 {
-  "title": "الرئيسية",
-  "description": "وصف صفحة الرئيسية",
-  "welcome": "مرحبًا",
-  "greeting": "مرحبًا بالعالم!",
-  "aboutPage": "صفحة حول",
-  "documentation": "التوثيق"
+  "title": "About",
+  "description": "About page description",
+  "counter": {
+    "label": "Counter",
+    "increment": "Increment",
+    "description": "Click the button to increase the counter"
+  }
 }
 ```
 
-```json fileName="src/locales/ar/about.json"
+ </Tab>
+ <Tab value='fr' label='الفرنسية'>
+
+```json fileName="src/locales/fr/about.json"
 {
-  "title": "حول",
-  "description": "وصف صفحة حول",
+  "title": "À propos",
+  "description": "Description de la page À propos",
   "counter": {
-    "label": "عداد",
-    "increment": "زيادة",
-    "description": "انقر على الزر لزيادة العداد"
+    "label": "Compteur",
+    "increment": "Incrémenter",
+    "description": "Cliquez sur le bouton pour augmenter le compteur"
   }
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={9} title="استخدام الترجمات في صفحاتك">

package/blog/ar/i18n_using_next-intl.md

@@ -316,6 +316,9 @@ export default async function AboutPage({
 
 تنظيم الترجمات حسب مساحة الأسماء (مثل `common.json`، `about.json`) يمكّن من تقسيم الكود وتقليل حجم الحزمة. تقوم بتحميل الترجمات اللازمة فقط لكل صفحة، مما يحسن الأداء.
 
+<Tabs group="locale">
+ <Tab value='en' label='الإنجليزية'>
+
 ```json fileName="locales/en/common.json"
 {
   "welcome": "Welcome",
@@ -323,6 +326,9 @@ export default async function AboutPage({
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='الفرنسية'>
+
 ```json fileName="locales/fr/common.json"
 {
   "welcome": "Bienvenue",
@@ -330,6 +336,12 @@ export default async function AboutPage({
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='الإنجليزية'>
+
 ```json fileName="locales/en/about.json"
 {
   "title": "About",
@@ -341,17 +353,23 @@ export default async function AboutPage({
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='الفرنسية'>
+
 ```json fileName="locales/fr/about.json"
 {
   "title": "À propos",
   "description": "Description de la page À propos",
   "counter": {
-    "label": "عداد",
-    "increment": "زيادة"
+    "label": "Compteur",
+    "increment": "Incrémenter"
   }
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={5} title="استخدام الترجمات في صفحاتك">

package/blog/de/i18n_using_next-i18next.md

@@ -453,6 +453,9 @@ Erstellen Sie JSON-Dateien für jede Locale und jeden Namespace. Diese Struktur
 
 Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.json`) ermöglicht Code-Splitting und reduziert die Bundle-Größe. So werden nur die Übersetzungen geladen, die für jede Seite benötigt werden, was die Performance verbessert.
 
+<Tabs group="locale">
+ <Tab value='en' label='Englisch'>
+
 ```json fileName="src/locales/en/common.json"
 {
   "appTitle": "Next.js i18n App",
@@ -460,6 +463,9 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='Französisch'>
+
 ```json fileName="src/locales/fr/common.json"
 {
   "appTitle": "Application Next.js i18n",
@@ -467,6 +473,12 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='Englisch'>
+
 ```json fileName="src/locales/en/home.json"
 {
   "title": "Home",
@@ -478,43 +490,25 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
-Organisieren von Übersetzungen nach Namespace (z. B. `common.json`, `about.json`) ermöglicht Code-Splitting und reduziert die Bundle-Größe. Sie laden nur die Übersetzungen, die für jede Seite benötigt werden, was die Leistung verbessert.
-
-```json fileName="src/locales/en/common.json"
-{
-  "appTitle": "Next.js i18n App",
-  "appDescription": "Beispiel einer Next.js-Anwendung mit Internationalisierung unter Verwendung von i18next"
-}
-```
+ </Tab>
+ <Tab value='fr' label='Französisch'>
 
-```json fileName="src/locales/de/common.json"
+```json fileName="src/locales/fr/home.json"
 {
-  "appTitle": "Next.js i18n App",
-  "appDescription": "Beispiel einer Next.js-Anwendung mit Internationalisierung unter Verwendung von i18next"
-}
-```
-
-```json fileName="src/locales/en/home.json"
-{
-  "title": "Home",
-  "description": "Home page description",
-  "welcome": "Welcome",
-  "greeting": "Hello, world!",
-  "aboutPage": "About Page",
+  "title": "Accueil",
+  "description": "Description de la page d'accueil",
+  "welcome": "Bienvenue",
+  "greeting": "Bonjour le monde!",
+  "aboutPage": "Page À propos",
   "documentation": "Documentation"
 }
 ```
 
-```json fileName="src/locales/de/home.json"
-{
-  "title": "Startseite",
-  "description": "Beschreibung der Startseite",
-  "welcome": "Willkommen",
-  "greeting": "Hallo, Welt!",
-  "aboutPage": "Über Seite",
-  "documentation": "Dokumentation"
-}
-```
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='Englisch'>
 
 ```json fileName="src/locales/en/about.json"
 {
@@ -528,18 +522,24 @@ Organisieren von Übersetzungen nach Namespace (z. B. `common.json`, `about.json
 }
 ```
 
-```json fileName="src/locales/de/about.json"
+ </Tab>
+ <Tab value='fr' label='Französisch'>
+
+```json fileName="src/locales/fr/about.json"
 {
-  "title": "Über",
-  "description": "Beschreibung der Über-Seite",
+  "title": "À propos",
+  "description": "Description de la page À propos",
   "counter": {
-    "label": "Zähler",
-    "increment": "Erhöhen",
-    "description": "Klicken Sie auf die Schaltfläche, um den Zähler zu erhöhen"
+    "label": "Compteur",
+    "increment": "Incrémenter",
+    "description": "Cliquez sur le bouton pour augmenter le compteur"
   }
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={9} title="Übersetzungen in Ihren Seiten verwenden">

package/blog/de/i18n_using_next-intl.md

@@ -315,6 +315,9 @@ Erstellen Sie JSON-Dateien für jede Locale und jeden Namespace. Diese Struktur
 
 Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.json`) ermöglicht Code-Splitting und reduziert die Bundle-Größe. Sie laden nur die Übersetzungen, die für jede Seite benötigt werden, was die Leistung verbessert.
 
+<Tabs group="locale">
+ <Tab value='en' label='Englisch'>
+
 ```json fileName="locales/en/common.json"
 {
   "welcome": "Welcome",
@@ -322,6 +325,9 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='Französisch'>
+
 ```json fileName="locales/fr/common.json"
 {
   "welcome": "Bienvenue",
@@ -329,6 +335,12 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='Englisch'>
+
 ```json fileName="locales/en/about.json"
 {
   "title": "About",
@@ -340,6 +352,9 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='Französisch'>
+
 ```json fileName="locales/fr/about.json"
 {
   "title": "À propos",
@@ -351,6 +366,9 @@ Die Organisation der Übersetzungen nach Namespace (z. B. `common.json`, `about.
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={5} title="Übersetzungen in Ihren Seiten verwenden">

package/blog/en/i18n_using_next-i18next.md

@@ -451,6 +451,9 @@ Create JSON files for each locale and namespace. This structure allows you to or
 
 Organizing translations by namespace (e.g., `common.json`, `about.json`) enables code splitting and reduces bundle size. You only load the translations needed for each page, improving performance.
 
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/common.json"
 {
   "appTitle": "Next.js i18n App",
@@ -458,6 +461,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/common.json"
 {
   "appTitle": "Application Next.js i18n",
@@ -465,6 +471,12 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/home.json"
 {
   "title": "Home",
@@ -476,6 +488,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/home.json"
 {
   "title": "Accueil",
@@ -487,6 +502,12 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/about.json"
 {
   "title": "About",
@@ -499,6 +520,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/about.json"
 {
   "title": "À propos",
@@ -511,6 +535,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={9} title="Utilize Translations in Your Pages">
@@ -1121,3 +1148,11 @@ And more. To discover all the features provided by Intlayer, please refer to the
 </Step>
 
 </Steps>
+
+<Sponsor>
+
+Once you have namespaces like common.json and about.json typed through i18next's module augmentation, you've effectively defined a content schema. The next question is where that schema lives and who edits it. Sanity treats it as first-class: you model fields, references, and validation in code, and editors work against that same model in Sanity Studio instead of hand-editing JSON per locale.
+
+Content lives in the Content Lake as structured JSON, queryable through GROQ and served via API, with locale as a field rather than a folder. For a Next.js App Router setup, you can fetch a namespace on the server, pass it into your i18n provider exactly as this pattern expects, and let the same source feed apps, emails, and agents. As locales and surfaces grow, the schema stays the contract; the delivery layer stays i18next.
+
+</Sponsor>

package/blog/en/i18n_using_next-intl.md

@@ -312,6 +312,9 @@ Create JSON files for each locale and namespace. This structure allows you to or
 
 Organizing translations by namespace (e.g., `common.json`, `about.json`) enables code splitting and reduces bundle size. You only load the translations needed for each page, improving performance.
 
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="locales/en/common.json"
 {
   "welcome": "Welcome",
@@ -319,6 +322,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="locales/fr/common.json"
 {
   "welcome": "Bienvenue",
@@ -326,6 +332,12 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="locales/en/about.json"
 {
   "title": "About",
@@ -337,6 +349,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="locales/fr/about.json"
 {
   "title": "À propos",
@@ -348,6 +363,9 @@ Organizing translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={5} title="Utilize Translations in Your Pages">

package/blog/en/rag_powered_documentation_assistant.md

@@ -302,11 +302,14 @@ That’s **product intelligence** straight from your users.
 
 </Steps>
 
-## Skip the Complexity with Sanity
+<Sponsor>
+
+### Skip the Complexity with Sanity
 
 Sanity is worth naming here as the CMS option the article points toward. Where Markdown files require arbitrary token splitting — with the chunk size and overlap trade-offs the article describes — Sanity's Content Lake stores documentation as typed, schema-defined JSON documents. Each field, heading, and content block is already a semantic unit, which means RAG retrieval operates on meaningful boundaries rather than approximate token counts.
 
 Sanity's GROQ query language lets you retrieve exactly the document fields relevant to a user query — title, body, related sections — without fetching the whole document. The MCP server connects the Content Lake directly to AI agents, so the same structured content that powers your docs site also feeds your RAG pipeline without a separate ingestion step.
+</Sponsor>
 
 ## Conclusion
 

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

@@ -451,13 +451,19 @@ Create JSON files for each locale and namespace. This structure allows you to or
 
 Organising translations by namespace (e.g., `common.json`, `about.json`) enables code splitting and reduces bundle size. You only load the translations needed for each page, improving performance.
 
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/common.json"
 {
   "appTitle": "Next.js i18n App",
-  "appDescription": "Example Next.js application with internationalisation using i18next"
+  "appDescription": "Example Next.js application with internationalization using i18next"
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/common.json"
 {
   "appTitle": "Application Next.js i18n",
@@ -465,6 +471,12 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/home.json"
 {
   "title": "Home",
@@ -476,6 +488,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/home.json"
 {
   "title": "Accueil",
@@ -487,6 +502,12 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="src/locales/en/about.json"
 {
   "title": "About",
@@ -499,6 +520,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="src/locales/fr/about.json"
 {
   "title": "À propos",
@@ -511,6 +535,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={9} title="Utilise Translations in Your Pages">

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

@@ -312,6 +312,9 @@ Create JSON files for each locale and namespace. This structure allows you to or
 
 Organising translations by namespace (e.g., `common.json`, `about.json`) enables code splitting and reduces bundle size. You only load the translations needed for each page, improving performance.
 
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="locales/en/common.json"
 {
   "welcome": "Welcome",
@@ -319,6 +322,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="locales/fr/common.json"
 {
   "welcome": "Bienvenue",
@@ -326,6 +332,12 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
+<Tabs group="locale">
+ <Tab value='en' label='English'>
+
 ```json fileName="locales/en/about.json"
 {
   "title": "About",
@@ -337,6 +349,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+ <Tab value='fr' label='French'>
+
 ```json fileName="locales/fr/about.json"
 {
   "title": "À propos",
@@ -348,6 +363,9 @@ Organising translations by namespace (e.g., `common.json`, `about.json`) enables
 }
 ```
 
+ </Tab>
+</Tabs>
+
 </Step>
 
 <Step number={5} title="Utilise Translations in Your Pages">