Description
"Internationalization, often shortened to "i18n", is the practice of designing a system in such a way that it can easily be adapted for different target audiences, that may vary in region, language, or culture."
What is the problem?
Although English is the dominant language in programming, English-only documentation may create a high barrier to entry for beginners, students, and non-native English speakers. Reading technical documentation in a foreign language maybe significantly harder for new developers (including myself) to get started (though not just for React Native but also other documentations too;)
How can we address it?
Since the documentation is built with Docusaurus, we could leverage the built-in Docusaurus i18n feature.
Why is it important?
As mentioned above, it makes the documentation much more accessible to a global audience. However, I understand that this is an optional feature and that maintaining multiple translations can create additional overhead for the core team.
Who needs this?
Beginners, students, and developers who are not fluent in English.
When should this happen (use version numbers if needed)?
Whenever feasible. Since this is an optional enhancement, it can be introduced at any time, though the initial setup will require some file structure changes to integrate the i18n system.
Related Issues, PRs:
#72(opened on Dec 15, 2017 🫨), #4367
Description
"Internationalization, often shortened to "i18n", is the practice of designing a system in such a way that it can easily be adapted for different target audiences, that may vary in region, language, or culture."
What is the problem?
Although English is the dominant language in programming, English-only documentation may create a high barrier to entry for beginners, students, and non-native English speakers. Reading technical documentation in a foreign language maybe significantly harder for new developers (including myself) to get started (though not just for React Native but also other documentations too;)
How can we address it?
Since the documentation is built with Docusaurus, we could leverage the built-in Docusaurus i18n feature.
Why is it important?
As mentioned above, it makes the documentation much more accessible to a global audience. However, I understand that this is an optional feature and that maintaining multiple translations can create additional overhead for the core team.
Who needs this?
Beginners, students, and developers who are not fluent in English.
When should this happen (use version numbers if needed)?
Whenever feasible. Since this is an optional enhancement, it can be introduced at any time, though the initial setup will require some file structure changes to integrate the i18n system.
Related Issues, PRs:
#72(opened on Dec 15, 2017 🫨), #4367