Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#5,259 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
react-native
Área
documentation, internationalization

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
MDX
Estrellas
2.2k
Forks
6.3k
Merge medio
13 h 6 min
PR fusionados (30 d)
28

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de react/react-native-website

Todos los issues de react/react-native-website

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.