[hi] Umbrella issue: Localize “Tasks” section into Hindi

[anushatomar13]

Description: The "Tasks" section in the Kubernetes documentation is currently available only in English, with the exception of the "Install Tools" subsection, which has been translated into Hindi. The following subsections do not have the Hindi translation despite of translating the documentation to Hindi (using the option on the website):

To make the documentation more accessible and inclusive for Hindi-speaking users, I would like to request the translation of the following subsections and the content within each subsection, under "Tasks" into Hindi:

• Administer a Cluster
• Configure Pods and Containers
• Monitoring, Logging, and Debugging
• Manage Kubernetes Objects
• Managing Secrets
• Inject Data Into Applications
• Run Applications
• Run Jobs
• Access Applications in a Cluster
• Extend Kubernetes
• TLS
• Manage Cluster Daemons
• Networking
• Extend kubectl with plugins
• Manage HugePages

Providing documentation in multiple languages can greatly benefit users who are more comfortable with their native language or have limited proficiency in English.

Please let me know if you need any further information or if I can start working on this issue.

Thanks a lot!

@divya-mohan0209 @arujjval @dipesh-rawat

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[sftim]

/retitle [hi] Umbrella issue: Localize “Tasks” section into Hindi /language hi

[sftim]

@anushatomar13 all localizations are actually a work-in-progress; there is no localization yet that has an equivalent page for each item of the English content.

Some are much further along than others, and that's fine. Most contributors to Kubernetes are volunteers.

[anushatomar13]

Thank you for the context, @sftim . I understand that the localization efforts are ongoing works in progress. As a Hindi speaker, I'm interested in helping to translate the 'Tasks' section into Hindi. Could you please guide me on the best way to get started and contribute to this effort? I'm happy to volunteer my time and follow any processes or guidelines to ensure my translations align with the project's standards. Thanks

[sftim]

There are slightly more than 200 task pages. I suggest you pick a small one and open an issue specifically about localizing that one task page. Mention “part of issue #46400” in the description of that new issue.

Also, if you're new to Kubernetes contribution overall, visit https://www.kubernetes.dev/docs/guide/first-contribution/

Then you can either:

• localize the page, and open a pull request. Kubernetes is open source which means you do not need permission to start helping
• ask for help to get started, for example in Slack. Visit https://slack.k8s.io for an invitation, then say hello in the #kubernetes-docs-hi and #kubernetes-new-contributors

---

Here is an example of a small task page: https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/

You would need to localize https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/ and also the index page, https://kubernetes.io/docs/tasks/access-application-cluster/ (mostly generated through automation, but you need to translate the page title).

[sftim]

We have a guide to localizing pages: https://kubernetes.io/docs/contribute/localization/

Please have a look at this and let us know if there are still questions after you have read it. It makes sense to us, but we don't know for sure whether the explanation makes sense to the target audience (new contributors who want to help with localization).

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[divya-mohan0209]

/remove-lifecycle stale

[VinayakPaka]

hi ! I would like to work on this issue. Can you please assign this issue to me.