[hi] Localize /en/docs/reference/glossary/application-architect.md

[rolfedh]

Instructions

• Review a few examples of localized glossary entries.
• In the examples, notice which elements are translated and which ones are not.

Translating the frontmatter

In the frontmatter, that is, between the --- markers that enclose the first dozen lines:

• Translate the title and short_description values.
• Do not translate the id, aka, tags values. We will systematically translate those later on in a separate project.

Translating the content body

Below the frontmatter, in the content body:

• Translate almost everything.
• If you encounter a glossary shortcode, for example, {{< glossary_tooltip text="containers" term_id="container" >}}, translate the text value. But do not translate the term_id value.

Procedure:

1. In this issue, assign this issue to yourself by commenting: /assign <your_github_id>
2. Open PR [WIP] [hi] Localize application-architect glossary term #35945.
3. In the PR, select all the lines in the file and click + to comment.
4. In the comment, click the +/- suggestion icon (screenshot 2).
5. In the suggestion, localize the content to Hindi.
6. IMPORTANT: Click the Start a review button.
7. IMPORTANT: Click Review changes, Comment, and Submit review.

Note: By completing these steps, your GitHub profile will give you credit for performing a code review!

As follow-up steps, I will do the following:

• Apply your suggested localization to the PR.
• Ask a reviewer to review the localized content.
• Update the content as needed.
• Get the PR approved and merged.

This feature issue is part of the following project:

• [hi] Umbrella issue for translating glossary entries to Hindi #35600

[bishal7679]

/triage accepted

[bishal7679]

/assign

[rolfedh]

/language hi

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[divya-mohan0209]

/remove-lifecycle rotten

[divya-mohan0209]

This has been fixed by #36084. Hence closing this issue.
/close

[k8s-ci-robot]

@divya-mohan0209: Closing this issue.

In response to this:

This has been fixed by #36084. Hence closing this issue.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.