[pt-br] Chapter01

[kmacedovarela]

[ptBR] Chapter01

• :gift: Adding portuguese translation

In addition, categorize the changes you're making using the "/kind" Prow command, example:

/kind documentation

Release Note

- Chapter 1 pt-br translation

Contributes to #26

[salaboy]

@kmacedovarela, this is awesome.. should we rename the file to pt_BR.md? so we follow the same approach with all languages.. I know that Matheus @mcruzdev wanted also to help.. so it might be good to distribute a bit the work.

[kmacedovarela]

We should absolutely follow a pattern of your choice. Unfortunately, I could not identify any ootb i18n feature for readme markdown files in GitHub, so it should be chosen based on trade-offs and your preferences :)

Things to consider....

• the book's target audience of readers [k8s]
• contributors[k8s, cloud-native],
• i18n industry standards,
• k8s docs chosen approach,
• clarity of assets names,
• and the fact that currently there is no more than one translation per language ( many country areas, e.g. pt_BR, pt_PT, zn_CN, zn_TW, and so on...)

...I'd suggest either

1. README.md, README-pt.md , README-zn.md. [my favorite, after some extra research]
2. README.md, README_pt.md , README_zn.md

Eventually if you get new translation prs from conflicting country areas (or if you already expect it), then you could reevaluate the strategy. =)

The only option I do 👎 is using the current option with two dots [README.pt-br.md], so thanks for considering other options :D

[salaboy]

I agree let's use the kubernetes approach with two letters from the iso like in this repo https://github.com/kubernetes/website/tree/main

[mcruzdev]

Hi @kmacedovarela @salaboy I am off today and tomorrow, but on Monday I want to help surely.