The discussion revolves around the need for a multilingual official Discourse webpage to better serve its diverse community. terraboss advocates for client-side language detection and collaborative translation efforts to reduce language barriers, especially for conservative decision-makers. gerhard confirms this is on the roadmap, previously blocked by website overhauls, now mostly completed. Moin shares an update that the webpage is now available in several languages, though inconsistencies in terminology (e.g., ‘Plugin’ vs. ‘Plug-in’) and content (e.g., ‘Anzeigen Plug in’ vs. ‘Werbung’) remain. terraboss enthusiastically welcomes the progress.
I believe, It’s time to translate the official Discourse webpage.
We have a great multilingual community solution. To convince new people to adapt Discourse, it’s necessary to reduce the borders in minds. Especially old / more conservative decision makers requesting more information in their native language. There is no question, that the admin it self’s could handle this within a dialog, but it costs me a lot of time and afford to repeat this over and over again.
I think, we should do a step forward and the Discourse core team should enable client-side language detection and the translation teams should work together for a diverse & multilingual first contact experience
What sometimes confuses me a little is that the same terms and spellings are not used as in the forum interface. Plug-in has always been corrected to the hyphenated version by the proofreaders. Also, in my forum, for example, it says “Anzeigen” (Advertisements) in the list of plug-ins, and in the price table, it says “Werbung” (Advertising) instead.
