Multi-lingual sourcing #32094
Replies: 7 comments 4 replies
-
Thank you for the issue. We do indeed plan to support this. While our strategy hasn't been officially decided, the easiest way to support it is probably by retrieving translations from resources where applicable. Plugin users would specify which languages they need in the Does that sound like something that could work for your case? |
Beta Was this translation helpful? Give feedback.
-
Could you maybe elaborate a little bit on the |
Beta Was this translation helpful? Give feedback.
-
You would for example pass something like this into plugin options:
Then perhaps we add something like this to our bulk query: fr_translations: translations(locale: "fr") {
key,
locale,
value
} And now your resource has a field |
Beta Was this translation helpful? Give feedback.
-
@sslotsky Perfectly fine 👍 |
Beta Was this translation helpful? Give feedback.
-
Any progress on this? I thought this would be available after all this time |
Beta Was this translation helpful? Give feedback.
-
https://www.gatsbyjs.com/resources/webinars/high-performance-localization-storyblok/ |
Beta Was this translation helpful? Give feedback.
-
Hello @sslotsky , any progress on this? Is there an alternative that we can use meanwhile? Thank you. |
Beta Was this translation helpful? Give feedback.
-
First things first: Thanks for the renewed Shopify source plugin.
Since you are now using Shopify’s Bulk Operations API, I wonder if there will be support for different languages as there is for quite some time in the Storefront API with the translation header?
From GatsbyConf 2021, I learned there will be multi-lingual support. Is there any timeline worth sharing or ready to do so? Any proof-of-concept to get an idea of how you will integrate this very important feature. More and more e-commerce sites are at least bi-lingual.
All the best,
Marco
Beta Was this translation helpful? Give feedback.
All reactions