Open Platonn opened 5 years ago
If the active language doesn't match any of the languages of the storefront, we should set the active language to the defaultLanguage of the store.
When navigating to a page in new language but in scope of the same Storefront's intance, it would be nice to:
Assigned 'future' label (post-1.0), because in 1.0 we won't support localizable routes.
Many Customers have CMS content in many different languages. Currently, we support switching language of CMS content using the site-context language switcher
Customers should be also able to configure the additional behaviour of site-context switcher - if and where to redirect after language change:
Cases to support
NOTE: This task should be started when #186 is done (the support of internationalized routes at one domain)
Possibly related topic: Multisite & multisite switcher