Skip to content
symbolflow logo
Docs

Native Multi-Language Setup & Content Management

For B2B exporters targeting buyers across North America, Europe, Latin America, and Asia, presenting a professional, native-language portal is fundamental to building buyer trust.

Appsuite features a fully automated, native multi-language pipeline. There is no need for fragile translation plugins or managing duplicate codebases.

1. How Native Multi-Language Works

Section titled “1. How Native Multi-Language Works”

Appsuite handles multilingual localization across three coordinated steps:

StepInterfaceOperational Action & Outcome
1. Define LanguagesSymbolFlow DashboardSelect supported locales during site setup or add new target languages (EN, ZH, ES, DE, FR, etc.) anytime in the dashboard.
2. Independent Content EntryPayload CMSUse the top-bar locale selector to enter tailored product titles, technical specs, and copy for each language.
3. Automated Static BuildAstro StorefrontWhen you deploy, the system compiles distinct localized URLs (e.g., /en/ and /zh/) with compliant hreflang metadata.

2. Managing Locales in the Dashboard

Section titled “2. Managing Locales in the Dashboard”

2.1 Initial Setup During Creation

Section titled “2.1 Initial Setup During Creation”

When creating an Appsuite from a template:

  1. Primary Default Language (Default Locale): The first language in the list serves as the site’s default locale (typically English (EN) for international B2B export sites).
    • Browser-Language Adaptive Redirection: When buyers access your root domain (e.g., www.myfactory.com), the edge gateway inspects their browser’s language preferences (Accept-Language). If a buyer uses a German browser and German is configured, they are automatically routed to /de/; if their browser language matches none of your enabled locales, the system smoothly falls back and redirects to this Default Locale (e.g., /en/).
    • Search Engine x-default Fallback: In the compiled HTML <head> across all pages, the system automatically injects <link rel="alternate" hreflang="x-default" href="..." /> pointing directly to this default language URL. This explicitly informs Google and global search engines to serve this version whenever no language or regional match is detected.
  2. Additional Locales: Click + Add Language to select from major global trade languages (Spanish, German, French, Italian, Japanese, Korean, Portuguese, Indonesian, Vietnamese, etc.).

    • Note: Russian (RU) is currently not supported. Furthermore, right-to-left (RTL) languages such as Arabic (AR) require a comprehensive restructuring of the frontend theme layout and are not currently supported. The system currently supports standard left-to-right (LTR) commercial locales.

2.2 Adding Locales Later

Section titled “2.2 Adding Locales Later”

If your business expands into a new territory (e.g., adding Spanish for Latin American clients):

  1. Navigate to your AppSuite Details in the SymbolFlow console.
  2. Locate the Supported Locales panel.
  3. Add the new target language and save.
  4. Your Payload CMS instance will immediately display the new locale in its editing dropdown.

3. Entering Localized Content in Payload CMS

Section titled “3. Entering Localized Content in Payload CMS”

When editing products (Offerings), regular pages (Pages), or headers (Header):

  1. Locate the Locale Selector: On the top toolbar of Payload Admin, you will see the active language tag (e.g., EN or ZH).
  2. Switching Context:
    • Switch to EN (English): Enter international mechanical nomenclature (e.g., Outer Diameter 20mm).
    • Switch to ZH (Chinese): Enter domestic Chinese product specifications.
  3. Identifying Localized Fields (Language Suffixes):
    • When a field label in Payload includes a language suffix code (e.g., Label — en or Title — zh), it indicates that the field is locale-dependent. You must supply distinct values for each language.
    • Shared universal fields (such as numeric unit prices, inventory counts, or relational links) do not carry language suffixes; updating them once applies globally.

3.1 Critical Note: Page Layouts Are Also Localized!

Section titled “3.1 Critical Note: Page Layouts Are Also Localized!”

Operators often ask: “Why did the new feature block I added to the English homepage not appear on the Chinese homepage?”

This is an intentional design engineered specifically for international trade:

  • The Design Rationale: B2B buyers in different geographic regions have distinct purchasing cultures. Western buyers often favor minimal layouts with case studies and ESG certifications, while Asian buyers may prioritize factory facility tours, lab equipment, and raw material provenance. Therefore, page Block layouts (layout) are strictly locale-dependent.
  • Operational Rule of Thumb:
    1. Adding, deleting, or reordering blocks in a page’s Layout only affects the currently active language.
    2. If you want structural parity across languages, after configuring the English layout (Layout — en), remember to switch to Chinese (Layout — zh) or your target language and apply the corresponding block adjustments there.

4. The International Buyer Experience

Section titled “4. The International Buyer Experience”

Once deployed, your global buyers experience a seamless native interface:

  • Header Language Switcher: A dropdown menu automatically appears in the top navigation bar.
  • Exact Path Persistence: Switching languages on the VD Mount page flips between /en/products/vd-cylindrical-rubber-damper and /zh/products/vd-cylindrical-rubber-damper without redirecting the buyer back to the home page.
  • Persistent Cart: A buyer adding 100 pcs in English will see their cart preserved when switching to Spanish or Chinese.

Next Steps

Section titled “Next Steps”