Allow users to switch between language versions of individual articles
complete
Emil Hajric
complete
🔥 We have a major new feature: Knowledge Base Localization / Translations.
You can now:
* Instantly deliver more support – without having to translate articles.
* Automatically translate your entire knowledge base, or article in 1 click.
* Translate any article side by side to 50+ languages!
* Deliver customer support in 50+ languages!
🔥 Read more: https://help.helpjuice.com/languages-and-translations/overview:-multiple-languages-&-localization
Deyana Stoeva
+1! This is a great feature request which our company is joining.
Currently we have more than 1100 published articles, with more than 60 in draft and we operatie (for now) in three different languages (EN, DE, FR).
- Use-case (internal challenge): Internal users who create and update content have difficulties keeping content up-to-date in different languages. As a SaaS company, we update our tool functionalities constantly and it is important for us to keep our customers informed all the time. We currently link each article manually after being translated by team members. It would be useful if we could see the parts that are not being translated or are missing in the other language.
- Use-case (external challenge): Many of our non-speaking clients are willing to use the knowledge base in their own language and are asking for such opportunity. The lack of it results in our customer operations teams being overwhelmed by the same question over and over again, thus increasing response time. It would be useful for clients after finding an article, for example, in EN language, to be able to open it immediately in another language.
Om Goeckermann
+1 here too
It would shorten our development cycle if we could allow a translator to access HJ and click an "Add Translation" button, select the language, and edit the new copy of that page. In this case, the articles would all be linked and your coding would be a language selector with some permissions stuff.
This should also be possible on bulk import because the original doc ID remains. Associating the newly created doc with the original should not be too hard.
Our first use-case is a user who has searched for content, found it, then discovers that other languages are offered. When they switch, they are sent to home page to begin searching. It is frustrating the first time, but once there, they should be able to stay on the chosen language.
This would be useful to help visitors who need a language we do not provide. Portuguese speaker, for instance, could use Italian and Spanish with the English to make sure they understand the content.
More importantly for us, being able to compare translations directly is important (to make minor changes or ensure appearance is good) and searching for pages in different languages is cumbersome, because HJ uses the language last set - therefore it is hard to have two open browsers with different languages and use the sites side by side.
Emil Hajric
Om Goeckermann: This would require us to re-engineer how translations work, which, to be hoenst, I'm 100% for.
I think we imlpemented it initially to support the idea of different areas require diff. articles.
Now I think that idea was not the best, so I'm for this. Thx for sharing your input w/ us
kathleen.kasey Kasey
+1 to this. This is critical to our success as we scale internationally
Emil Hajric
kathleen.kasey Kasey: Thanks for letting us know Kathleen!
Henry Cheang
This would be a WONDERFUL addition to Helpjuice. Currently, we have to manually link independent articles. It was manageable in the beginning, but we now have over 400 articles per language. It's becoming harder and harder to manage the links.