New Admin page headers now contain hardcoded links to meta’s documentation pages. Some Discourse messages also contain links to meta.
I would like to keep translating some or possibly all of them. I believe that whatever appears in the UI should be localized, otherwise it is a mixed experience for the end user.
I already translated some of the first articles every user is offered (e.g. when they are first upgraded to a new trust level). As my intention is to start a local community and promote Discourse in my country (especially for enterprise users), I believe some of the frequent guides should be localized. So I started a local Discourse “meta”. At the end of every translated article I mention the original article. So far I chose a few articles that are quite stable and don’t change a lot. Sometimes I check if they are up to date.
I put the localized URL to the resource translations. I know this might be controversial but since it was possible, I tried it. Therefore the following article for example has 2k views since 1 year.
For me it would be enough to provide the hardcoded admin page links (DPageHeader.learnMoreUrl) in the resources so they can be localized if needed.
I am wondering if someone from the product team could give an eye on my question? I know I am maybe going too far with the localization but these are actually critical documents that are kept in English. And my experience so far is that ordinary internet people actually have sometimes a hard time onboarding to Discourse, as it is not WhatsApp or Facebook and there is a learning path and a part of it is not in their mother tongue. Same goes for admins sometimes.
So at some point, one thing that we may consider doing based on your input here is to have links from discourse to our documentation automatically take users to the translated version of the page.
I’m shooting from the hip a bit here… @nat and @hugh, any thoughts on what I’m suggesting above?
Hey Tomas, there is active development in our discourse-translator plugin as Dave has mentioned above.
The ultimate goal for this is to have a Discourse for everyone — where we can converse across all languages. What this means exactly is that we will give Discourse community owners the ability to translate all posts (automatically) to languages of their choice. In addition, community users will be able to set up Discourse such that all content (controls, topics, posts) are displayed in their language.
This is currently an experimental feature, and there are some details on how this all works. I will be announcing this properly on meta soon™ as I fix some of the minor bugs.
I put the localized URL to the resource translations. I know this might be controversial but since it was possible, I tried it. Therefore the following article for example has 2k views since 1 year.