Any plans for adding Internationalization (i18n) Support for react-native documentation?
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 30/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 活躍
- 技術堆疊
- react-native
研究方向
Start by reviewing the Docusaurus i18n feature documentation and the related issues #72 and #4367. Determine the required documentation structure changes, supported languages, and maintenance approach; the work is complete when React Native documentation has a defined, maintainable internationalization setup.
由索引模型根據 Issue 內容生成。
描述
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
- 主要語言
- MDX
- 星號
- 2.2k
- 分支
- 6.3k
- 平均合併
- 13 小時 6 分鐘
- 30 天內合併 PR
- 28
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
react/react-native-website 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 76/100
react/react-native-website#5258 ·
維護者通常 1 天內回覆
-
Docs: distinguish Fast Refresh effect reruns from Strict Mode checks可能已有人在做 @walitemuri 於 24 天前認領。 未關閉
難度 1/5 1-3 小時 新手友好度 88/100
react/react-native-website#5217 ·
維護者通常 1 天內回覆
-
Integration with Existing Apps: Podfile example does not use `use_react_native!`, is incomplete可能已有人在做 @mhjacobson 於 1701 天前認領。 未關閉👋 Good first issue
難度 1/5 1 小時以內 新手友好度 78/100
react/react-native-website#2958 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 48/100
react/react-native-website#5216 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 42/100
react/react-native-website#5154 · 6 則留言 ·
維護者通常 1 天內回覆
查看 react/react-native-website 的全部 Issue
相似的 Issue
-
changelog investigate
難度 2/5 1-3 小時 新手友好度 62/100
ramnes/notion-sdk-py#409 ·
-
難度 1/5 1 小時以內 新手友好度 78/100
salesforce/multicloudj#667 ·
維護者通常 1 天內回覆
-
bug needs-triage
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆
-
End of term: remove the PerfForesightCRRA-Approximation stub, and redirect its econ-ark.org page未關閉
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 2 天內回覆
-
Bug pulumi/pulumi
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆