Improve localizaiton contribution guide

a-mccarthy commented 11 months ago

This is a Feature Request Improve the localization contribution guide to include more information about maintain localization teams as well as improve clarity for new contributors looking to help a localization and new localization teams starting their translation journey.

page to update: https://kubernetes.io/docs/contribute/localization/

This issue is based off the discussion that happened here: https://github.com/kubernetes/website/discussions/42409

What would you like to be added

We should break up the Localization Contribution guide into 3 pages that focus on

Contributing to a localization
Starting a new localization team
Maintaining a localization

@seokho-son proposed this page structure for this section. bold section titles are new content areas.

Contribute to an existing localization
- Fork and clone the repo
- Find your two-letter language code
- Suggest changes
- Localize content
- ...
- Localize SVG images
- Upstream contributions
Localizing Kubernetes documentation (includes 3 sub-pages)
- Start a new localization
- Find community
- Join the Kubernetes GitHub organization
- Add your localization team in GitHub
- Configure the workflow
- Modify the site configuration
- Add a new localization directory
- Localize the community code of conduct
- Setting up the OWNERS files
- Site strings in i18n
- Open a pull request
- Add a localized README file
- Minimum required content (add link to Localize content)
- Launching your new localization
Maintain an existing localization
(Importance of long term stability of the localization)
Language-specific localization guide
Language-specific Zoom meetings
Source files
Branching strategy

a-mccarthy commented 11 months ago

@seokho-son I've moved the localization contribution guide improvements into an issue. I think the first step is to create a PR with the new page structure and get that merged, then work on adding in the new content sections. What do you think?