Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Any plans for adding Internationalization (i18n) Support for react-native documentation?

Offen
  • Stimmt etwas nicht?
#5,259 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
30/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
react-native
Bereich
documentation, internationalization

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
MDX
Sterne
2.2k
Forks
6.3k
Ø Merge
13 Std. 6 Min.
Gemergte PRs (30 T.)
28

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus react/react-native-website

Alle Issues in react/react-native-website

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.