Hello community!
Today, I want to talk about an idea that I believe may not be entirely new, but I haven't seen many approaches to it, so I decided to write it in a more structured way.
(The most similar idea I found was this: Translation Teams)
The idea is allowing community members to contribute in translating OutSystems documentation. I'll explain why and how I envision this implementation.
Why?
Regardless of the language we speak, we all prefer reading and hearing our mother tongue, as it resonates differently in our hearts. A study in the NeuroImage journal concluded that there are structural differences in the brain connections of people with different native languages. (Native language differences in the structural connectome of the human brain)
If our mother tongue influences our brain in this way, it will undoubtedly impact how we learn, whether in our native language or in a language learned later in life, such as English.
Considering this, I believe translated documentation can significantly enhance a user's information processing, accelerating their learning and development.
But what about English? We all know it's crucial for developers to read and communicate in English for various reasons. Documentation helps in this!
Yes, I don't deny that. My goal is not to translate all content or dismiss English. I propose implementing translation to help in studying/understanding documentation.
How?
The idea is simple. Community members submit translated documentation to OutSystems. The translation team (if it exists) reviews and, upon approval, makes it available.
Questions may arise:
How many languages?
Translating documentation into every language is unrealistic. Initially, I suggest translating into the world's top 5 or 10 most spoken languages, covering a large audience and gauging project success.
Members suggesting translations? That's crazy! There could be errors or trolls!
Various measures can prevent these scenarios. I propose limiting the number of members suggesting translations:
- Only active or higher-ranked members can suggest translations;
- Members with specific certifications/proven technical knowledge can suggest translations;
- Only MVPs or Champions can suggest translations;
- Members must apply for a "translation program", proving linguistic abilities for specific articles/languages;
- A combination of the above.
Members could use tools like Google Translate or AI!
True. For that members might be evaluated for translation skills, and OutSystems could verify translations. Using translation tools doesn't necessarily mean poor quality; it just requires validation.
OutSystems just did this with AI translation for Japanese!
Yes and no. While OutSystems' implementation is excellent for forums, it may not suit documentation. AI may not grasp documentation contexts, leading to empty translations. Reliable translations by professionals understanding the original message, context, and technical aspects would be more valuable than AI translations.
This is my idea. It's complex and may not be as easy to implement as it seems. It would take time and effort, but I believe it would be a great addition to this constantly evolving community in need of skilled developers. This implementation would not only expand OutSystems' reach but also enhance every user's experience and learning!
Please share your thoughts on my idea. If you have questions, ask, and I'll respond if I can. Support it if you find it valid and would like to see it implemented.
Cheers,
Mauro Alviza