[Translation] Guide Translation to Portuguese Brasil (pt-br)

[felipe-heredia]

This question will be used to

a. Organize the process of translating the entire website to pt-br.
b. To gather all the information about the status of the translation of the whole website to pt-br.
c. Track all-volunteer translators (to know which part of the website they are translating, to avoid conflicts during the whole process).

If you would like to volunteer, you can comment below on which page you will be working on the translation, so that everyone knows.

Note: The main folder is /content/pt-br/

---

The docs pages translated:

• Index (including Header and Footer).
• docs/1.get-started
• docs/2.concepts
• docs/3.features
• docs/4.directory-structure
• docs/5.configuration-glossary
• docs/6.internals-glossary
• docs/7.components-glossary

[trizotti]

You guys are doing an amazing job translating to pt-BR! Can I help somehow? 😄

[felipe-heredia]

Welcome, @trizotti. I'm Actually translating the docs/3.features. Can you help me with this? This section is so big.

However, if you don't want to help me with docs/3.features, you can translate any other section, I just ask you to tell here what you are doing.

[trizotti]

Sure I can help with the 'docs' page! @felipesuri , any suggestion on how I could help with the 'docs' page? Is there any specific section you'd like to recommend for some parallel work?

[trizotti]

Progress of translation for 'Examples' page:

• 1.routing
• 2.data-fetching
• 3.assets-management
• 4.transitions
• 5.seo
• 6.loading
• 7.miscellaneous
• 8.middlewares
• 9.plugins
• 10.modules

[felipe-heredia]

@trizotti I must recommend that you translate the docs/4.directory-structure docs section.

Here are some tips to get a better translation:

• Add i18n config in the nuxt.config file, like this: But never commit it, because this is for better work of the site in development, we can't push this change

i18n: {
  locales: [
    ...,
    {
        code: 'pt-br',
        iso: 'pt-BR',
        file: 'pt-BR.js',
        name: 'Português (Brasil)'
    },
  ]
]

• Disable any lint extension like markdownlint because it can break the site, I've been there and it's not cool.
• Revise the entire page after the translation and click on every link and make sure they keep working.
• When you open PR, mention this issue on there I will revise it before the others reviewers.
• Use Docus and Portuguese - Code Spell Checker extensions on VSCode.

[trizotti]

Hello, @felipesuri ! I've finished the translation for the 'Examples' page, but I'm a little bit confused on how to define the replacements for the titles highlighted with green boxes:

[felipe-heredia]

@trizotti for this, you'll need to translate the title on each index.md file.

Ex.:

---
title: Rotas
navigation:
  collapse: false
  redirect: /examples/routing/hello-world
---

This code is on the examples/1.routing/index.md file.

[MonicaFidalgo]

Awesome work everyone!! I would love to contribute as well! :)
Is there something that I can help with? Translating some missing page/docs or helping review prs?
Thanks!