15

Hi @patricia. Thanks for all your insights here. I have a related question for the group: I’m currently building a single-page application that already relies heavily on URL routing (via @sudsy’s excellent Sudsy plugin) and conditional logic to pull in the appropriate UI components for each page.

I’m interested in implementing a multilingual strategy and have been considering the following approach:

  • Create top-level domain folders for each target language
  • Have a language toggle in header that would allow users to switch to their native language and redirect to appropriate URL
  • For each text element: Have default text in english, custom state to store translated text and conditional logic based on URL language-folder to toggle between the two
  • Translated text would be generated via a conditional workflow on page load that would call Google Translate’s API when the URL structure dictated

I like this strategy because it would allow us to activate new markets with almost zero incremental cost. The appropriate HREFlang tags would be added to our master template page — with the language, again, being populated dynamically. With that said, the biggest cost to us would be making duplicates of that base page for each language.

I imagine I’m overlooking some hurdles here so would love to hear your thoughts, as well as those of @romanmg and @AliFarahat.

Cheers!