Merge branch 'main' into PAPI-3321

bc-tayvs · web-flow · commit 4bd49e170286 · 2026-01-21T22:37:42.000+02:00
diff --git a/docs/storefront/catalyst/features/localization/multi-language/overview.mdx b/docs/storefront/catalyst/features/localization/multi-language/overview.mdx
@@ -4,7 +4,7 @@ Catalyst supports translating content into multiple languages on a single storef
 
 This reference describes tools for managing translations for dynamic product catalog data. It includes managing language settings, detecting shopper preferences based on browser settings or shopper input, and switching between languages on the storefront.
 
-For information on how to manage translations for the storefront theme, see the [Static Translations](/docs/storefront/catalyst/content-management/internationalization/static-translations) guide.
+For information on how to manage translations for the storefront theme, see the [Static Translations](/docs/storefront/catalyst/features/localization/static-translations) guide.
 
 ## Content management
 
@@ -90,7 +90,7 @@ To render dynamic product data, GraphQL Storefront API supports fetching languag
 
 ### Translate checkout & transactional emails
 
-You can localize your checkout page by translating fixed text elements, known as static strings, into multiple languages. Static string translations are managed using [JSON files in your Catalyst project](/docs/storefront/catalyst/content-management/internationalization/static-translations), where each file contains the language-specific translations. For translation keys that checkout supports, see the [Enabling Multi-Language Checkout](https://developer.bigcommerce.com/docs/storefront/cart-checkout/localization#adding-your-own-translation-values) article. You can also use translation keys to translate emails using the [Email Template](https://developer.bigcommerce.com/docs/rest-content/email-templates#update-a-template) endpoints of the REST Content API.
+You can localize your checkout page by translating fixed text elements, known as static strings, into multiple languages. Static string translations are managed using [JSON files in your Catalyst project](/docs/storefront/catalyst/features/localization/static-translations), where each file contains the language-specific translations. For translation keys that checkout supports, see the [Enabling Multi-Language Checkout](https://developer.bigcommerce.com/docs/storefront/cart-checkout/localization#adding-your-own-translation-values) article. You can also use translation keys to translate emails using the [Email Template](https://developer.bigcommerce.com/docs/rest-content/email-templates#update-a-template) endpoints of the REST Content API.
 
 By default, BigCommerce offers translations for the checkout page and emails in 19 languages. You can view the [full list of supported languages](https://developer.bigcommerce.com/docs/storefront/cart-checkout/localization#adding-your-own-translation-values) that we automatically provide.
 
diff --git a/docs/storefront/catalyst/features/localization/multi-language/setup.mdx b/docs/storefront/catalyst/features/localization/multi-language/setup.mdx
@@ -93,9 +93,9 @@ Let’s explore more of how this works! Static string translations are already p
 
 <Video src={"https://storage.googleapis.com/bigcommerce-production-dev-center/videos/catalyst/static%20french%20translations.mov"} />
 
-As you’ve noticed, after you enable a supported locale, the text for some components on your page will already be translated into this language. But if your locale is unsupported, you’ll need to [define your own static string translations](/docs/storefront/catalyst/content-management/internationalization/static-translations#translation-file) in this directory.
+As you’ve noticed, after you enable a supported locale, the text for some components on your page will already be translated into this language. But if your locale is unsupported, you’ll need to [define your own static string translations](/docs/storefront/catalyst/features/localization/static-translations#translation-file) in this directory.
 
-When you create more components, you’ll want to access the translations from your file. Learn more about [how to use the translations](/docs/storefront/catalyst/content-management/internationalization/static-translations#using-keys-in-react-components) inside your Client and Server Components.
+When you create more components, you’ll want to access the translations from your file. Learn more about [how to use the translations](/docs/storefront/catalyst/features/localization/static-translations#using-keys-in-react-components) inside your Client and Server Components.
 
 ## Translating dynamic data from BigCommerce
 
diff --git a/docs/storefront/catalyst/features/localization/multi-storefront/overview.mdx b/docs/storefront/catalyst/features/localization/multi-storefront/overview.mdx
@@ -24,7 +24,7 @@ The storefront content to localize includes the following:
 
 Learn more in the [Getting Started with Localization on Multi-Storefronts](https://support.bigcommerce.com/s/article/Getting-Started-with-Localization-on-Multi-Storefronts) support article.
 
-You can localize the storefront theme using [static translations](/docs/storefront/catalyst/content-management/internationalization/static-translations).
+You can localize the storefront theme using [static translations](/docs/storefront/catalyst/features/localization/static-translations).
 
 ## Locale-specific URLs
 
diff --git a/docs/storefront/catalyst/features/localization/multi-storefront/setup.mdx b/docs/storefront/catalyst/features/localization/multi-storefront/setup.mdx
@@ -95,13 +95,13 @@ One current limitation is that you can only assign a specific locale to one stor
 
 ### Static data
 
-Each locale that we want to include on our storefronts – in our case  `en`, `fr`, and `de` – has text elements that need language translations. Learn more about how to [translate those text elements into multiple languages](/docs/storefront/catalyst/content-management/internationalization/multi-language/setup#translating-static-strings) in the tutorial.
+Each locale that we want to include on our storefronts – in our case  `en`, `fr`, and `de` – has text elements that need language translations. Learn more about how to [translate those text elements into multiple languages](/docs/storefront/catalyst/features/localization/multi-language/setup#translating-static-strings) in the tutorial.
 
 If you're using Makeswift, you'll need to add the same locales that you added in your Control Panel.
 
 ![Makeswift locales](https://storage.googleapis.com/bigcommerce-production-dev-center/images/catalyst/multi-storefront/makeswift%20locales.png)
 
-For more details on customizing content in Makeswift, check out the [Translating Makeswift content](/docs/storefront/catalyst/content-management/internationalization/multi-language/setup#translating-makeswift-content) section.
+For more details on customizing content in Makeswift, check out the [Translating Makeswift content](/docs/storefront/catalyst/features/localization/multi-language/setup#translating-makeswift-content) section.
 
 
 ### Dynamic data
@@ -150,7 +150,7 @@ When you visit the “Shop All” category, you should see products you added to
 
 <Video src={"https://storage.googleapis.com/bigcommerce-production-dev-center/videos/catalyst/Products%20MSF%20Catalyst.mov"} />
 
-Learn how to translate the products and categories into French and German in the [Localizing a Storefront into Multiple Languages](/docs/storefront/catalyst/content-management/internationalization/multi-language/setup#translating-dynamic-data-from-bigcommerce) tutorial.
+Learn how to translate the products and categories into French and German in the [Localizing a Storefront into Multiple Languages](/docs/storefront/catalyst/features/localization/multi-language/setup#translating-dynamic-data-from-bigcommerce) tutorial.
 
 #### Pricing
 
diff --git a/docs/storefront/catalyst/features/localization/overview.mdx b/docs/storefront/catalyst/features/localization/overview.mdx
@@ -1,4 +1,4 @@
-# Internationalization
+# Localization
 
 You can localize your Catalyst storefront so that it appears in the shopper's preferred culture or language throughout their browsing and checkout experience.
 
@@ -12,7 +12,7 @@ Catalyst supports the following scenarios:
 
     This approach is particularly common if you want unique shopping experiences for different countries like France and Germany. While each storefront is customized for its target audience, merchants often interlink the sites, enabling shoppers to choose their preferred country's website for purchases.
 
-    For how to implement this use case, see the [Catalyst Multi-Storefront Guide](/docs/storefront/catalyst/content-management/internationalization/multi-storefront/setup).
+    For how to implement this use case, see the [Catalyst Multi-Storefront Guide](/docs/storefront/catalyst/features/localization/multi-storefront/setup).
 <br />
 
 1. **Single storefront setup for multi-language**: You are selling within a country and would like to accommodate multiple languages within that country.
@@ -21,7 +21,7 @@ Catalyst supports the following scenarios:
 
     With a single storefront setup, the shopper's experience remains consistent, but the content is displayed in their preferred language. This use case is particularly common in multilingual countries like Canada, where the same storefront serves shoppers in two primary languages without altering the overall user experience.
 
-    For how to implement this use case, see the [Catalyst Multi-Language Guide](/docs/storefront/catalyst/content-management/internationalization/multi-language/setup).
+    For how to implement this use case, see the [Catalyst Multi-Language Guide](/docs/storefront/catalyst/features/localization/multi-language/setup).
 
     Catalyst also allows you to combine both approaches. For example, you can create multiple storefronts for regions like France, the UK, and Belgium, while further customizing the Belgian storefront to support three languages within a single store.
 
diff --git a/docs/storefront/catalyst/features/localization/static-translations.mdx b/docs/storefront/catalyst/features/localization/static-translations.mdx
diff --git a/docs/storefront/headless/index.mdx b/docs/storefront/headless/index.mdx
@@ -249,7 +249,7 @@ Including a visitor ID in session sync requests helps maintain a cohesive sessio
 
 ## Multi-Language support
 
-After **October 2025**, new headless stores will have access to Multi-language features similar to [Catalyst storefronts](/docs/storefront/catalyst/content-management/internationalization/multi-language/overview).
+After **October 2025**, new headless stores will have access to Multi-language features similar to [Catalyst storefronts](/docs/storefront/catalyst/features/localization/multi-language/overview).
 
 ## Next step
 
