@intlayer/docs 7.0.7 → 7.0.8-canary.0

package/blog/en-GB/intlayer_with_i18next.md

@@ -40,14 +40,23 @@ See a concrete comparison with i18next in our [next-i18next vs. next-intl vs. In
 
 While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with i18next for several reasons:
 
-1. **Existing codebase**: You have an established i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with i18next but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation keys management, translation status, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for i18next to help automate your JSON translations in CLI or CI/CD pipelines, test your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with i18next.
+However, **i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **i18next**, you get the best of both worlds — i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for i18next**, allowing you to:
+
+- Gradually migrate from i18next to Intlayer.
+- Keep existing i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 

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

@@ -49,15 +49,25 @@ See a concrete comparison with next-intl in our [next-i18next vs. next-intl vs.
 
 ## Why Combine Intlayer with next-i18next?
 
-While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_nextjs_16.md)), you might want to combine it with next-i18next for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_nextjs_16.md)), you might want to combine it with next-i18next for several reasons.
 
-1. **Existing codebase**: You have an established next-i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with next-i18next but wants better content management.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for next-i18next to help automate your JSON translations in CLI or CI/CD pipelines, test your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with next-i18next.
+However, **i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **i18next**, you get the best of both worlds — i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for i18next**, allowing you to:
+
+- Gradually migrate from i18next to Intlayer.
+- Keep existing i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ---
 

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

@@ -25,15 +25,25 @@ See a concrete comparison with next-intl in our [next-i18next vs. next-intl vs.
 
 ## Why Combine Intlayer with next-intl?
 
-While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md)), you might want to combine it with next-intl for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [Next.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_nextjs_16.md)), you might want to combine it with next-intl for several reasons.
 
-1. **Existing codebase**: You have an established next-intl implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing next-intl plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with next-intl but desires better content management.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you.
 
-**For this, Intlayer can be implemented as an adapter for next-intl to assist in automating your JSON translations in CLI or CI/CD pipelines, testing your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide demonstrates how to leverage Intlayer's superior content declaration system while maintaining compatibility with next-intl.
+However, **next-intl** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **next-intl**, you get the best of both worlds — next-intl’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for next-intl**, allowing you to:
+
+- Gradually migrate from next-intl to Intlayer.
+- Keep existing next-intl plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 

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

@@ -36,16 +36,25 @@ See a concrete comparison with react-i18next in our [react-i18next vs. react-int
 
 ## Why Combine Intlayer with react-i18next?
 
-While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)), you might want to combine it with react-i18next for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_vite+react.md)), you might want to combine it with react-i18next for several reasons.
 
-1. **Existing codebase**: You have an established react-i18next implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing react-i18next plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with react-i18next but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for react-i18next to help automate your JSON translations in CLI or CI/CD pipelines, test your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system whilst maintaining compatibility with react-i18next.
+However, **react-i18next** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **react-i18next**, you get the best of both worlds — react-i18next’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for react-i18next**, allowing you to:
+
+- Gradually migrate from react-i18next to Intlayer.
+- Keep existing react-i18next plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Table of Contents
 

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

@@ -38,20 +38,25 @@ See a concrete comparison with react-intl in our [react-i18next vs. react-intl v
 
 ## Why Combine Intlayer with react-intl?
 
-While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)), you might want to combine it with react-intl for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [React integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_vite+react.md)), you might want to combine it with react-intl for several reasons:
 
-1. **Existing codebase**: You have an established react-intl implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing react-intl plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with react-intl but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for react-intl to help automate your JSON translations in CLI or CI/CD pipelines, test your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system while maintaining compatibility with react-intl.
+However, **react-intl** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
 
-## Table of Contents
+By combining **Intlayer** with **react-intl**, you get the best of both worlds — react-intl’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
 
-<TOC/>
+This guide explains how to leverage Intlayer as an **adapter for react-intl**, allowing you to:
+
+- Gradually migrate from react-intl to Intlayer.
+- Keep existing react-intl plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ## Step-by-Step Guide to Set Up Intlayer with react-intl
 

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

@@ -38,16 +38,25 @@ See a concrete comparison with vue-i18n in our [vue-i18n vs. Intlayer](https://g
 
 ## Why Combine Intlayer with vue-i18n?
 
-While Intlayer provides an excellent standalone i18n solution (see our [Vue.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+vue.md)), you might want to combine it with vue-i18n for several reasons:
+While Intlayer provides an excellent standalone i18n solution (see our [Vue.js integration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_vite+vue.md)), you might want to combine it with vue-i18n for several reasons.
 
-1. **Existing codebase**: You have an established vue-i18n implementation and want to gradually migrate to Intlayer's improved developer experience.
-2. **Legacy requirements**: Your project requires compatibility with existing vue-i18n plugins or workflows.
-3. **Team familiarity**: Your team is comfortable with vue-i18n but wants better content management.
-4. **Using Intlayer features**: You want to use Intlayer features like content declaration, translation automation, testing translations, and more.
+Intlayer offers a rich set of **advanced features** that go beyond traditional i18n tools. It helps you:
 
-**For that, Intlayer can be implemented as an adapter for vue-i18n to help automate your JSON translations in CLI or CI/CD pipelines, test your translations, and more.**
+- **Automatically detect and fill missing translations** to streamline localization.
+- **Test and validate your translations** directly in your development or CI/CD workflows.
+- **Manage content per component**, enabling a clean, scalable, and maintainable structure across your app.
+- **Externalize your content**, making it easily editable by your whole team (developers, translators, and content managers).
 
-This guide shows you how to leverage Intlayer's superior content declaration system whilst maintaining compatibility with vue-i18n.
+However, **vue-i18n** remains an excellent and widely adopted i18n solution thanks to its **mature ecosystem**, **broad community support**, and **extensive plugin compatibility**.
+
+By combining **Intlayer** with **vue-i18n**, you get the best of both worlds — vue-i18n’s stability and ecosystem maturity, with Intlayer’s modern content management, automation, and developer experience improvements.
+
+This guide explains how to leverage Intlayer as an **adapter for vue-i18n**, allowing you to:
+
+- Gradually migrate from vue-i18n to Intlayer.
+- Keep existing vue-i18n plugins and workflows.
+- Automate your JSON translations in CLI or CI/CD pipelines.
+- Test, sync, and manage translations more effectively.
 
 ---
 

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

@@ -35,6 +35,8 @@ We focus on **Next.js 13+ App Router** (with **React Server Components**) and ev
 6. **Developer experience (DX), tooling & maintenance**
 7. **SEO & large-project scalability**
 
+<TOC/>
+
 > **tl;dr**: All three can localise a Next.js app. If you want **component-scoped content**, **strict TypeScript types**, **build-time missing-key checks**, **tree-shaken dictionaries**, and **first-class App Router + SEO helpers**, **Intlayer** is the most complete, modern choice.
 
 > One confusion often made by developers is to think that `next-intl` is the Next.js version of `react-intl`. It's not—`next-intl` is maintained by [Amann](https://github.com/amannn), while `react-intl` is maintained by [FormatJS](https://github.com/formatjs/formatjs).

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

@@ -32,6 +32,8 @@ We evaluate:
 - Developer experience (DX), tooling & maintenance
 - SEO/routing (framework-dependent)
 
+<TOC/>
+
 > **tl;dr**: All three can localise a React app. If you want **component-scoped content**, **strict TypeScript types**, **build-time missing-key checks**, **tree-shaken dictionaries**, and built-in editorial tooling (Visual Editor/CMS + optional AI translation), **Intlayer** is the most complete choice for modular React codebases.
 
 ---

package/blog/en-GB/vue-i18n_vs_intlayer.md

@@ -30,6 +30,8 @@ We focus on modern Vue tooling (Vite, Composition API) and evaluate:
 6. **Developer experience (DX), tooling & maintenance**
 7. **SEO & large-project scalability**
 
+<TOC/>
+
 > **tl;dr**: Both can localise Vue apps. If you want **component-scoped content**, **strict TypeScript types**, **build-time missing-key checks**, **tree-shaken dictionaries**, and **batteries-included router/SEO helpers** plus **Visual Editor & AI translations**, **Intlayer** is the more complete, modern choice.
 
 ---