Venia - CIF Category and Product pages Translation | Community
Skip to main content
rajeevy89244319
rajeevy89244319
Level 3
February 23, 2024
Solved

Venia - CIF Category and Product pages Translation

  • February 23, 2024
  • 2 replies
  • 563 views

I am looking into Venia reference site built using cif. If a page is not created for product, it creates virtual page from the template for the url if the product exist.

 

I am curious to know how the translation for these pages will work if we want to use translation engine in aem? Since actual page does exist and I try to hit fr page  then it will still be picking the template from en version.

 

As any one used cif with translations or else give pointers? What’s are the best practices for handling translations with cif and Venia reference website?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Raja_Reddy

    Hi @rajeevy89244319 

    1. Configure AEM for translation: Set up AEM to support translation by configuring the necessary translation connectors and services. This typically involves integrating with a translation management system (TMS) or using AEM's built-in translation capabilities.

    2. Create translated content pages: In AEM, create translated content pages for each language you want to support. These translated pages should have the same structure and components as the original English pages.

    3. Use language-specific templates: Create language-specific templates in AEM that are associated with the translated content pages. These templates should have the same structure and components as the original English template but with language-specific configurations.

    4. Enable language fallback: Configure language fallback in AEM to ensure that if a translated page is not available, the user is redirected to the default language page or a fallback language page.

    5. Implement language switcher: Add a language switcher component to the Venia reference site to allow users to switch between different language versions of the site. This component should update the language parameter in the URL and redirect the user to the corresponding translated page.

    6. Translate product information: Use AEM's translation capabilities or integrate with a TMS to translate product information, such as names, descriptions, and attributes. This can be done by creating language-specific product catalogs or by using translation connectors to send product information for translation.

    7. Implement language-specific URL structure: Configure AEM to generate language-specific URLs for translated pages. This can be done using AEM's language copy feature or by customizing the URL structure based on language.

    8. Test and validate translations: Test the translated pages and ensure that all content, including product information, is correctly translated and displayed on the Venia reference site.
      https://techforum.medium.com/aem-and-magento-integration-using-commerce-integration-framework-cif-local-setup-part2-8bf77a3d5c3a 
      https://github.com/adobe/aem-cif-guides-venia 

    2 replies

    Imran Khan
    Community Advisor
    Imran KhanCommunity Advisor
    Community Advisor
    February 23, 2024

    @rajeevy89244319 Use MSM language copy feature to translate pages into respective language and at the same time use one of the translation engines available in market.

      Raja_Reddy
      Community Advisor
      Raja_ReddyCommunity AdvisorAccepted solution
      Community Advisor
      February 24, 2024

      Hi @rajeevy89244319 

      1. Configure AEM for translation: Set up AEM to support translation by configuring the necessary translation connectors and services. This typically involves integrating with a translation management system (TMS) or using AEM's built-in translation capabilities.

      2. Create translated content pages: In AEM, create translated content pages for each language you want to support. These translated pages should have the same structure and components as the original English pages.

      3. Use language-specific templates: Create language-specific templates in AEM that are associated with the translated content pages. These templates should have the same structure and components as the original English template but with language-specific configurations.

      4. Enable language fallback: Configure language fallback in AEM to ensure that if a translated page is not available, the user is redirected to the default language page or a fallback language page.

      5. Implement language switcher: Add a language switcher component to the Venia reference site to allow users to switch between different language versions of the site. This component should update the language parameter in the URL and redirect the user to the corresponding translated page.

      6. Translate product information: Use AEM's translation capabilities or integrate with a TMS to translate product information, such as names, descriptions, and attributes. This can be done by creating language-specific product catalogs or by using translation connectors to send product information for translation.

      7. Implement language-specific URL structure: Configure AEM to generate language-specific URLs for translated pages. This can be done using AEM's language copy feature or by customizing the URL structure based on language.

      8. Test and validate translations: Test the translated pages and ensure that all content, including product information, is correctly translated and displayed on the Venia reference site.
        https://techforum.medium.com/aem-and-magento-integration-using-commerce-integration-framework-cif-local-setup-part2-8bf77a3d5c3a 
        https://github.com/adobe/aem-cif-guides-venia 

        Terms & ConditionsAccessibility statement

        Loading footer...