add zh pages

content/zh/docs/concepts/architecture/cloud-controller.md

@@ -1,19 +1,19 @@
 ---
 title: 云控制器管理器的基础概念
-content_template: templates/concept
+content_type: concept
 weight: 30
 ---
 
 <!--
 ---
 title: Concepts Underlying the Cloud Controller Manager
-content_template: templates/concept
+content_type: concept
 weight: 30
 ---
 -->
 
 
-{{% capture overview %}}
+<!-- overview -->
 
 <!--
 The cloud controller manager (CCM) concept (not to be confused with the binary) was originally created to allow cloud specific vendor code and the Kubernetes core to evolve independent of one another. The cloud controller manager runs alongside other master components such as the Kubernetes controller manager, the API server, and scheduler. It can also be started as a Kubernetes addon, in which case it runs on top of Kubernetes.
@@ -45,10 +45,10 @@ Here's the architecture of a Kubernetes cluster without the cloud controller man
 
 ![没有云控制器管理器的 Kubernetes 架构](/images/docs/pre-ccm-arch.png)
 
-{{% /capture %}}
 
 
-{{% capture body %}}
+
+<!-- body -->
 
 <!--
 ## Design
@@ -496,5 +496,5 @@ Complete instructions for configuring and running the CCM are provided
 
 [这里](/docs/tasks/administer-cluster/running-cloud-controller/#cloud-controller-manager)提供了有关配置和运行 CCM 的完整说明。
 
-{{% /capture %}}
+
 

content/zh/docs/concepts/architecture/controller.md

@@ -1,10 +1,10 @@
 ---
 title: 控制器
-content_template: templates/concept
+content_type: concept
 weight: 30
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 <!--
 In robotics and automation, a _control loop_ is
 a non-terminating loop that regulates the state of a system.
@@ -25,10 +25,10 @@ closer to the desired state, by turning equipment on or off.
 
 {{< glossary_definition term_id="controller" length="short">}}
 
-{{% /capture %}}
 
 
-{{% capture body %}}
+
+<!-- body -->
 <!--
 ## Controller pattern
 
@@ -244,11 +244,12 @@ Deployment 控制器和 Job 控制器是 Kubernetes 内置控制器的典型例
 
 你会发现控制平面外面运行的控制器，扩展了 Kubernetes 的能力。或者，如果你愿意，你也可以写一个新控制器。你可以以一组 Pod 来运行你的控制器，或者运行在 Kubernetes 外面。什么是最合适的控制器，这将取决于特定控制器的功能。
 
-{{% /capture %}}
 
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 * 请阅读 [Kubernetes 控制平面](/docs/concepts/#kubernetes-control-plane)
 * 了解一些基本的 [Kubernetes 对象](/docs/concepts/#kubernetes-objects)
 * 学习更多的 [Kubernetes API](/docs/concepts/overview/kubernetes-api/)
 * 如果你想写自己的控制器，请看 Kubernetes 的[扩展模式](/docs/concepts/extend-kubernetes/extend-cluster/#extension-patterns)。
-{{% /capture %}}
+

content/zh/docs/concepts/architecture/nodes.md

@@ -1,6 +1,6 @@
 ---
 title: 节点
-content_template: templates/concept
+content_type: concept
 weight: 10
 ---
 <!--
@@ -9,12 +9,12 @@ reviewers:
 - caesarxuchao
 - dchen1107
 title: Nodes
-content_template: templates/concept
+content_type: concept
 weight: 10
 ---
 -->
 
-{{% capture overview %}}
+<!-- overview -->
 
 <!--
 A node is a worker machine in Kubernetes, previously known as a `minion`. A node
@@ -27,10 +27,10 @@ architecture design doc for more details.
 在 Kubernetes 中，节点（Node）是执行工作的机器，以前叫做 `minion`。根据你的集群环境，节点可以是一个虚拟机或者物理机器。每个节点都包含用于运行 [pods](/docs/concepts/workloads/pods/pod/) 的必要服务，并由主控组件管理。节点上的服务包括 [容器运行时](/docs/concepts/overview/components/#node-components)、kubelet 和 kube-proxy。查阅架构设计文档中 [Kubernetes 节点](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node) 一节获取更多细节。
 
 
-{{% /capture %}}
 
 
-{{% capture body %}}
+
+<!-- body -->
 
 <!--
 ## Node Status
@@ -527,12 +527,13 @@ API object can be found at:
 -->
 节点是 Kubernetes REST API 的顶级资源。更多关于 API 对象的细节可以在这里找到：[节点 API 对象](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#node-v1-core)。
 
-{{% /capture %}}
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 <!--
 * Read about [node components](https://kubernetes.io/docs/concepts/overview/components/#node-components)
 * Read about node-level topology: [Control Topology Management Policies on a node](/docs/tasks/administer-cluster/topology-manager/)
 -->
 * 了解有关[节点组件](https://kubernetes.io/docs/concepts/overview/components/#node-components)的信息。
 * 阅读有关节点级拓扑的信息：[控制节点上的拓扑管理策略](/docs/tasks/administer-cluster/topology-manager/)。
-{{% /capture %}}
+