I can't give you estimate when we start looking into multilingual features
there might be a way today to do that by connecting to some backend api that allows for translations, but we haven't looked into current solutions, so I can't give you recomendations or tutorials
maybe @John Siciliano wants to look into it
Webflow are charging $30 a month per locale (!) for proper localization, as if it's only enterprises who need translation :S
@voytado You can check out Weglot. They have a simple javascript implementation.. downside of this is the translations won't impact SEO. But if you're not relying on SEO or just need translations for like menus or something then this will work. They also have reverse proxy to solve the SEO side, but haven't dove too far into that
https://www.weglot.com/technical-presentationweglot won't work, they are a bolt-on solution over dns afaik they don't have a concept for an app that can update depending on a client-logic
basically they only would work for static sites, which send html they can rewrite and that's it, unless I didn't dig deep enough
then it won't be able to server-render different languages, it would first load original language, then in-browser rewrite it, this would suck 10x
I think the best way to solve multilingual is to do it on data layer
wherever is the content defined
Forsure would be better to serve it from the backend. But most likely would require a lot more work. Depends on the needs of the site if its worth it or not IMO
Well with the CMS launch if cms supports multilingual features, this should be basically done
Also need to make a checklist of everything needed to be able to use dynamic data we already launched for multi-lingual.
Afaik we need to be able to pick up the language code from the url and use that language variable when fetching Resource with the right language.
I think we are suprt close to being able to do this.
@TrySound can we launch path query and using those path variables as a standalone launch even before we hit CMS?
I think this has potential to solve a lot of problems for a lot of people.
for context, you will be able to say something like in page settings for the Path
/:lang/my-page
and then in the Resource url you could use something like:
/some-resource/${pageData.lang}
So you have as many languages as you want and they can fetch from a corresponding url.
You would be able to use any content provider that has multilingual features or even build your own on top of a database.
Im not sure. It all sounds like cms
Yes, no integration of something specific but ready to use infrastructure
exactly, I think it makes sense to launch this separately
so we can start making tutorials on how to use it for different use cases with different services
So it is cms support launch without specific one.
Not single click solution
I think this would be a fantastic launch.
we could make not one but 5 different examples and if its easy enough, tis is going to show how flexible the system is instead of just one integration where people will find enough reasons why it doesn't work for them.
Maybe we get it to the point where a CMS like Strapi is just a template, nothing special at the integration level.
