# Localizing Kubernetes documentation

Localizing Kubernetes documentationThis page shows you how to localize the docs for a different language.Contribute to an existing localizationYou can help add or improve the content of an existing localization. In Kubernetes Slack, you can find a channel for each localization. There is also a general SIG Docs Localizations Slack channel where you can say hello.Note:For extra details on how to contribute to a specific localization, look for a localized version of this page.Find your two-letter language codeFirst, consult the ISO 639-1 standard to find your localization's two-letter language code. For example, the two-letter code for Korean is ko.Some languages use a lowercase version of the country code as defined by the ISO-3166 along with their language codes. For example, the Brazilian Portuguese language code is pt-br.Fork and clone the repoFirst, create your own fork of the kubernetes/website repository.Then, clone your fork and cd into it:git clone https://github.com/<username>/website cd website The website content directory includes subdirectories for each language. The localization you want to help out with is inside content/<two-letter-code>.Suggest changesCreate or update your chosen localized page based on the English original. See localize content for more details.If you notice a technical inaccuracy or other problem with the upstream (English) documentation, you should fix the upstream documentation first and then repeat the equivalent fix by updating the localization you're working on.Limit changes in a pull requests to a single localization. Reviewing pull requests that change content in multiple localizations is problematic.Follow Suggesting Content Improvements to propose changes to that localization. The process is similar to proposing changes to the upstream (English) content.Start a new localizationIf you want the Kubernetes documentation localized into a new language, here's what you need to do.Because contributors can't approve their own pull requests, you need at least two contributors to begin a localization.All localization teams must be self-sufficient. The Kubernetes website is happy to host your work, but it's up to you to translate it and keep existing localized content current.You'll need to know the two-letter language code for your language. Consult the ISO 639-1 standard to find your localization's two-letter language code. For example, the two-letter code for Korean is ko.If the language you are starting a localization for is spoken in various places with significant differences between the variants, it might make sense to combine the lowercased ISO-3166 country code with the language two-letter code. For example, Brazilian Portuguese is localized as pt-br.When you start a new localization, you must localize all the minimum required content before the Kubernetes project can publish your changes to the live website.SIG Docs can help you work on a separate branch so that you can incrementally work towards that goal.Find communityLet Kubernetes SIG Docs know you're interested in creating a localization! Join the SIG Docs Slack channel and the SIG Docs Localizations Slack channel. Other localization teams are happy to help you get started and answer your questions.Please also consider participating in the SIG Docs Localization Subgroup meeting. The mission of the SIG Docs localization subgroup is to work across the SIG Docs localization teams to collaborate on defining and documenting the processes for creating localized contribution guides. In addition, the SIG Docs localization subgroup looks for opportunities to create and share common tools across localization teams and identify new requirements for the SIG Docs Leadership team. If you have questions about this meeting, please inquire on the SIG Docs Localizations Slack channel.You can also create a Slack channel for your localization in the kubernetes/community repository. For an example of adding a Slack channel, see the PR for adding a channel for Persian.Join the Kubernetes GitHub organizationWhen you've opened a localization PR, you can become members of the Kubernetes GitHub organization. Each person on the team needs to create their own Organization Membership Request in the kubernetes/org repository.Add your localization team in GitHub