Concerns about performance: when user will go from page to page, the setTranslations/loadTranslations will be called every time (so a fetch to translations API, right?). Load function works both: on server and front end side. It will slow down navigation. Especially if the translations will be a big set. This is another performance concern, the function loads translations for every page no matter on which we are, right? But the idea and the demo are brilliant! It could be killer for every headless CMS in a future :)
> setTranslations/loadTranslations will be called every time (so a fetch to translations API, right?) I believe it's only fetching on initial load. I am not 100% sure though. Regarding your performance concerns: All correct. Splitting translations via route is relatively easy with the approach shown in the video. > But the idea and the demo are brilliant! It could be killer for every headless CMS in a future :) Version 0.2 just landed! inlang.dev/blog/inlang-v0-2 . Different approach as shown in the video because the approach in the video does not work for SEO purposes. But, I intend to bring it back for apps. I am looking for insights how developers i18n their software and feedback for inlang. Do you have experiences in i18n software?
@@samuelstroschein Nice. Thanks for the answer. I have i18n experience. I work in company where we build multilingual sites and ecommerces. Usually we use NextJS and Storyblok as CMS for small and medium size projects. I am looking for better solutions though. Svelte with Inlang seems a better choice. Sometimes it is hard to convince clients to a new solutions. Time will show :)
@@cis84muz Thanks for the reply! Curious to hear more about the problems you experienced with NextJS + Storyblok in the context of i18n. Can you send me a mail to inlang@inlang (dot) dev, or book a short call with me here calendly.com/samuelstroschein/quick-chat ?
I assume blog posts/full articles are best translated as individual files. Headless CMS services already provide that functionality (or at least should) e.g. language "en" -> post.en.markdown etc.
Hi James! What a conincidence. I was just pushing this commit 3 minutes ago github.com/inlang/inlang/commit/6ac4206202e46a4c33e17e4a719beeb186f3d5bd. I expect the website, and thus app, to go live this week! Bear in mind, a lot has changed in the past 12 months. The approach differs from what you see in the video but, ultimately, what's coming should make localization much simpler. Feel free to write me a mail samuel[DOT]stroschein[AT]inlang.com if you want to be notified
@@samuelstroschein Great news, exciting project and perfect timing for SvelteKit 1.0. I only saw this comment because I had to double check the video again to see how easy things should be after looking at all the other options available am trying some that didn't work out too well with latest version of SvelteKit.
great. I just learned about svelte. And saw this by chance. Nice video. Great tool!
Thanks! Have you tried it out?
@@samuelstroschein I have no use for it at the moment. Just toying around with svelte
Concerns about performance: when user will go from page to page, the setTranslations/loadTranslations will be called every time (so a fetch to translations API, right?). Load function works both: on server and front end side. It will slow down navigation. Especially if the translations will be a big set. This is another performance concern, the function loads translations for every page no matter on which we are, right?
But the idea and the demo are brilliant! It could be killer for every headless CMS in a future :)
> setTranslations/loadTranslations will be called every time (so a fetch to translations API, right?)
I believe it's only fetching on initial load. I am not 100% sure though.
Regarding your performance concerns:
All correct. Splitting translations via route is relatively easy with the approach shown in the video.
> But the idea and the demo are brilliant! It could be killer for every headless CMS in a future :)
Version 0.2 just landed! inlang.dev/blog/inlang-v0-2 . Different approach as shown in the video because the approach in the video does not work for SEO purposes. But, I intend to bring it back for apps.
I am looking for insights how developers i18n their software and feedback for inlang. Do you have experiences in i18n software?
@@samuelstroschein Nice. Thanks for the answer. I have i18n experience. I work in company where we build multilingual sites and ecommerces. Usually we use NextJS and Storyblok as CMS for small and medium size projects. I am looking for better solutions though. Svelte with Inlang seems a better choice. Sometimes it is hard to convince clients to a new solutions. Time will show :)
@@cis84muz Thanks for the reply! Curious to hear more about the problems you experienced with NextJS + Storyblok in the context of i18n. Can you send me a mail to inlang@inlang (dot) dev, or book a short call with me here calendly.com/samuelstroschein/quick-chat ?
I like this for shorter or fewer text elements. But what would you suggest for larger articles of text? Like a blog post, or documentation content?
I assume blog posts/full articles are best translated as individual files. Headless CMS services already provide that functionality (or at least should) e.g. language "en" -> post.en.markdown etc.
When can we use it? Been over a year now.. do we self host
Hi James! What a conincidence. I was just pushing this commit 3 minutes ago github.com/inlang/inlang/commit/6ac4206202e46a4c33e17e4a719beeb186f3d5bd. I expect the website, and thus app, to go live this week!
Bear in mind, a lot has changed in the past 12 months. The approach differs from what you see in the video but, ultimately, what's coming should make localization much simpler. Feel free to write me a mail samuel[DOT]stroschein[AT]inlang.com if you want to be notified
@@samuelstroschein Great news, exciting project and perfect timing for SvelteKit 1.0. I only saw this comment because I had to double check the video again to see how easy things should be after looking at all the other options available am trying some that didn't work out too well with latest version of SvelteKit.
wow, 7 views. Make more videos👍