One way to contribute to Angular's documentation is to localize it into another language. This topic describes what you need to know to localize Angular and have it listed on our Localized documentation page.
Before you start localizing the Angular documentation, first check to see if a localized version already exists. See Localized documentation for a current list of localized versions of Angular documentation.
To have a localized version of Angular documentation listed on angular.io, you must either:
Nomination, in this instance, means that the GDE knows who you are and can vouch for your capabilities. An Angular GDE can nominate someone by contacting the Angular team, providing your name, contact information, and the language to which you are localizing.
To localize Angular documentation, you must include, at a minimum, the following topics:
Because these topics reflect the minimum documentation set for localization, the Angular documentation team takes special precautions when making any changes to these topics. Specifically:
Individuals and teams that localize Angular documentation assume responsibility for hosting their localized site. The Angular team does not host localized content. The Angular team is also not responsible for providing domain names.
As part of the localization effort, the Angular documentation team adds localized documentation to the Localized documentation page. This topic lists:
The Angular team can remove a link on this page for any reason, including but not limited to:
The Angular documentation team uses a Slack channel to communicate with members of the community focused on localization efforts. After receiving a nomination to localize content, an individual or team can contact the Angular team to get access to this Slack channel.
The Angular documentation team may also conduct meetings to discuss localization efforts. For example:
© 2010–2022 Google, Inc.
Licensed under the Creative Commons Attribution License 4.0.
https://angular.io/guide/localizing-angular