Merge pull request #39881 from my-git9/hugo-shortcodes

[zh-cn]sync docs/contribute

Author: k8s-ci-robot

content/zh-cn/docs/concepts/configuration/overview.md

@@ -211,7 +211,7 @@ to others, please don't hesitate to file an issue or submit a PR.
   rate.
 -->
 - 定义并使用[标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/)来识别应用程序
-  或 Deployment 的 **语义属性**，例如 `{ app.kubernetes.io/name: MyApp, tier: frontend, phase: test, deployment: v3 }`。
+  或 Deployment 的**语义属性**，例如 `{ app.kubernetes.io/name: MyApp, tier: frontend, phase: test, deployment: v3 }`。
   你可以使用这些标签为其他资源选择合适的 Pod；
   例如，一个选择所有 `tier: frontend` Pod 的服务，或者 `app.kubernetes.io/name: MyApp` 的所有 `phase: test` 组件。
   有关此方法的示例，请参阅 [guestbook](https://github.com/kubernetes/examples/tree/master/guestbook/) 。

content/zh-cn/docs/contribute/localization.md

@@ -64,18 +64,27 @@ standard](https://www.loc.gov/standards/iso639-2/php/code_list.php) to find your
 localization's two-letter language code. For example, the two-letter code for
 Korean is `ko`.
 
-### Fork and clone the repo
-
-First, [create your own
-fork](/docs/contribute/new-content/open-a-pr/#fork-the-repo) of the
-[kubernetes/website](https://github.com/kubernetes/website) repository.
+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`.
 -->
 ### 找到两个字母的语言代码 {#find-your-two-letter-language-code}
 
 首先，有关本地化的两个字母的语言代码，请参考
 [ISO 639-1 标准](https://www.loc.gov/standards/iso639-2/php/code_list.php)。
 例如，韩语的两个字母代码是 `ko`。
 
+一些语言使用 ISO-3166 定义的国家代码的小写版本及其语言代码。
+例如，巴西葡萄牙语代码是 `pt-br`。
+
+
+<!--
+### Fork and clone the repo
+
+First, [create your own
+fork](/docs/contribute/new-content/open-a-pr/#fork-the-repo) of the
+[kubernetes/website](https://github.com/kubernetes/website) repository.
+-->
 ### 派生（fork）并且克隆仓库 {#fork-and-clone-the-repo}
 
 首先，为 [kubernetes/website](https://github.com/kubernetes/website) 仓库
@@ -155,6 +164,20 @@ You'll need to know the two-letter language code for your language. Consult the
 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`.
+-->
+你需要知道你的语言的两个字母的语言代码。
+请查阅 [ISO 639-1 标准](https://www.loc.gov/standards/iso639-2/php/code_list.php)
+以查找你的本地化的两字母语言代码。例如，韩语的两字母代码是 `ko`。
+
+如果你开始本地化的语言在不同地方使用，并且变体之间存在显着差异，
+则将小写的 ISO-3166 国家/地区代码与语言双字母代码结合起来可能是有意义的。
+例如，巴西葡萄牙语被本地化为 `pt-br`。
+
+<!--
 When you start a new localization, you must localize all the
 [minimum required content](#minimum-required-content) before
 the Kubernetes project can publish your changes to the live
@@ -163,10 +186,6 @@ website.
 SIG Docs can help you work on a separate branch so that you
 can incrementally work towards that goal.
 -->
-你需要知道你的语言的两个字母的语言代码。
-请查阅 [ISO 639-1 标准](https://www.loc.gov/standards/iso639-2/php/code_list.php)
-以查找你的本地化的两字母语言代码。例如，韩语的两字母代码是`ko`。
-
 当你开始新的本地化时，你必须先本地化所有[最少要求的内容](#minimum-required-content)，
 Kubernetes 项目才能将你的更改发布到当前网站。
 
@@ -633,11 +652,11 @@ To find source files for your target version:
 1. Navigate to the Kubernetes website repository at https://github.com/kubernetes/website.
 2. Select a branch for your target version from the following table:
 
-   Target version | Branch
-   -----|-----
-   Latest version | [`main`](https://github.com/kubernetes/website/tree/main)
-   Previous version | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}})
-   Next version | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}})
+Target version | Branch
+-----|-----
+Latest version | [`main`](https://github.com/kubernetes/website/tree/main)
+Previous version | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}})
+Next version | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}})
 
 The `main` branch holds content for the current release `{{< latest-version >}}`. 
 The release team creates a `{{< release-branch >}}` branch before the next
@@ -653,11 +672,11 @@ release: v{{< skew nextMinorVersion >}}.
 1. 导航到 Kubernetes website 仓库，网址为 https://github.com/kubernetes/website。
 2. 从下面的表格中选择你的目标版本分支：
 
-   目标版本 | 分支
-   -----|-----
-   最新版本 | [`main`](https://github.com/kubernetes/website/tree/main)
-   上一个版本 | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}})
-   下一个版本 | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}})
+目标版本 | 分支
+-----|-----
+最新版本 | [`main`](https://github.com/kubernetes/website/tree/main)
+上一个版本 | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}})
+下一个版本 | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}})
 
 `main` 分支中保存的是当前发行版本 `{{< latest-version >}}` 的内容。
 发行团队会在下一个发行版本 v{{< skew nextMinorVersion >}} 出现之前创建

content/zh-cn/docs/contribute/style/hugo-shortcodes/index.md

@@ -448,6 +448,63 @@ Renders to:
 {{< tab name="JSON File" include="podtemplate.json" />}}
 {{< /tabs >}}
 
+<!--
+### Source code files
+You can use the `{{</* codenew */>}}` shortcode to embed the contents of file
+in a code block to allow users to download or copy its content to their clipboard.
+This shortcode is used when the contents of the sample file is generic and reusable, 
+and you want the users to try it out themselves.
+-->
+你可以使用 `{{</* codenew */>}}` 短代码将文件内容嵌入代码块中，
+以允许用户下载或复制其内容到他们的剪贴板。
+当示例文件的内容是通用的、可复用的，并且希望用户自己尝试使用示例文件时，
+可以使用此短代码。
+
+<!--
+This shortcode takes in two named parameters: `language` and `file`. 
+The mandatory parameter `file` is used to specify the path to the file
+being displayed. The optional parameter `language` is used to specify
+the programming language of the file. If the `language` parameter is not provided,
+the shortcode will attempt to guess the language based on the file extension.
+
+For example:
+-->
+这个短代码有两个命名参数：`language` 和 `file`，
+必选参数 `file` 用于指定要显示的文件的路径，
+可选参数 `language` 用于指定文件的编程语言。
+如果未提供 `language` 参数，短代码将尝试根据文件扩展名推测编程语言。
+
+```none
+{{</* codenew language="yaml" file="application/deployment-scale.yaml" */>}}
+```
+
+<!--
+The output is:
+-->
+输出是：
+
+{{< codenew language="yaml" file="application/deployment-scale.yaml" >}}
+
+<!--
+When adding a new sample file, such as a YAML file, create the file in one
+of the `<LANG>/examples/` subdirectories where `<LANG>` is the language for
+the page. In the markdown of your page, use the `codenew` shortcode:
+-->
+添加新的示例文件（例如 YAML 文件）时，在 `<LANG>/examples/`
+子目录之一中创建该文件，其中 `<LANG>` 是页面的语言。
+在你的页面的 markdown 文本中，使用 `codenew` 短代码：
+
+```none
+{{</* codenew file="<RELATIVE-PATH>/example-yaml>" */>}}
+```
+
+其中 `<RELATIVE-PATH>` 是要包含的示例文件的路径，相对于 `examples` 目录。
+以下短代码引用位于 `/content/en/examples/configmap/configmaps.yaml` 的 YAML 文件。
+
+```none
+{{</* codenew file="configmap/configmaps.yaml" */>}}
+```
+
 <!--
 ## Third party content marker
 -->

content/zh-cn/docs/contribute/style/style-guide.md

@@ -974,12 +974,8 @@ Do | Don't
 Update the title in the front matter of the page or blog post. | Use first level heading, as Hugo automatically converts the title in the front matter of the page into a first-level heading.
 Use ordered headings to provide a meaningful high-level outline of your content. | Use headings level 4 through 6, unless it is absolutely necessary. If your content is that detailed, it may need to be broken into separate articles.
 Use pound or hash signs (`#`) for non-blog post content. | Use underlines (`---` or `===`) to designate first-level headings.
-Use sentence case for headings in the page body. For example,
-**Extend kubectl with plugins** | Use title case for headings in the page body. For example, **Extend Kubectl With Plugins**
-Use title case for the page title in the front matter. For example,
-`title: Kubernetes API Server Bypass Risks` | Use sentence case for page titles
-in the front matter. For example, don't use
-`title: Kubernetes API server bypass risks`
+Use sentence case for headings in the page body. For example, **Extend kubectl with plugins** | Use title case for headings in the page body. For example, **Extend Kubectl With Plugins**
+Use title case for the page title in the front matter. For example, `title: Kubernetes API Server Bypass Risks` | Use sentence case for page titles in the front matter. For example, don't use `title: Kubernetes API server bypass risks`
 {{< /table >}}
 -->
 {{< table caption = "标题约定" >}}
@@ -1342,9 +1338,11 @@ These steps ... | These simple steps ...
 <!--
 * Learn about [writing a new topic](/docs/contribute/style/write-new-topic/).
 * Learn about [using page templates](/docs/contribute/style/page-content-types/).
+* Learn about [custom hugo shortcodes](/docs/contribute/style/hugo-shortcodes/).
 * Learn about [creating a pull request](/docs/contribute/new-content/open-a-pr/).
 -->
 * 了解[编写新主题](/zh-cn/docs/contribute/style/write-new-topic/)。
 * 了解[页面内容类型](/zh-cn/docs/contribute/style/page-content-types/)。
+* 了解[定制 Hugo 短代码](/zh-cn/docs/contribute/style/hugo-shortcodes/)。
 * 了解[发起 PR](/zh-cn/docs/contribute/new-content/open-a-pr/)。