Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#5,259 1 comentário 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
react-native
Domínio
documentation, internationalization

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
MDX
Estrelas
2.2k
Forks
6.3k
Merge médio
13h 6min
PRs com merge (30d)
28

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de react/react-native-website

Todas as issues de react/react-native-website

Issues semelhantes

Mais issues de Documentation

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.