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.