Apply concept template to extend-kubernetes and configuration dirs (#8995)

content/en/docs/concepts/configuration/assign-pod-node.md

@@ -4,9 +4,14 @@ reviewers:
 - kevin-wangzefeng
 - bsalamat
 title: Assigning Pods to Nodes
+content_template: templates/concept
 weight: 30
 ---
 
+{{< toc >}}
+
+{{% capture overview %}}
+
 You can constrain a [pod](/docs/concepts/workloads/pods/pod/) to only be able to run on particular [nodes](/docs/concepts/architecture/nodes/) or to prefer to
 run on particular nodes. There are several ways to do this, and they all use
 [label selectors](/docs/concepts/overview/working-with-objects/labels/) to make the selection.
@@ -19,7 +24,9 @@ services that communicate a lot into the same availability zone.
 You can find all the files for these examples [in our docs
 repo here](https://github.com/kubernetes/website/tree/{{< param "docsbranch" >}}/docs/concepts/configuration/).
 
-{{< toc >}}
+{{% /capture %}}
+
+{{% capture body %}}
 
 ## nodeSelector
 
@@ -332,3 +339,9 @@ For more information on inter-pod affinity/anti-affinity, see the
 
 You may want to check [Taints](/docs/concepts/configuration/taint-and-toleration/)
 as well, which allow a *node* to *repel* a set of pods.
+
+{{% /capture %}}
+
+{{% capture whatsnext %}}
+
+{{% /capture %}}

content/en/docs/concepts/configuration/secret.md

@@ -2,15 +2,22 @@
 reviewers:
 - mikedanese
 title: Secrets
+content_template: templates/concept
 weight: 50
 ---
 
+{{< toc >}}
+
+{{% capture overview %}}
+
 Objects of type `secret` are intended to hold sensitive information, such as
 passwords, OAuth tokens, and ssh keys.  Putting this information in a `secret`
 is safer and more flexible than putting it verbatim in a `pod` definition or in
 a docker image. See [Secrets design document](https://git.k8s.io/community/contributors/design-proposals/auth/secrets.md) for more information.
 
-{{< toc >}}
+{{% /capture %}}
+
+{{% capture body %}}
 
 ## Overview of Secrets
 
@@ -638,11 +645,10 @@ The `secret-volume` will contain a single file, called `.secret-file`, and
 the `dotfile-test-container` will have this file present at the path
 `/etc/secret-volume/.secret-file`.
 
-**NOTE**
-
-Files beginning with dot characters are hidden from the output of  `ls -l`;
+{{< note >}}
+**Note**: Files beginning with dot characters are hidden from the output of  `ls -l`;
 you must use `ls -la` to see them when listing directory contents.
-
+{{< /note >}}
 
 ### Use-case: Secret visible to one container in a pod
 
@@ -751,3 +757,7 @@ Pod level](#use-case-secret-visible-to-one-container-in-a-pod).
 {{< note >}}
 **Note:** As of 1.7 [encryption of secret data at rest is supported](/docs/tasks/administer-cluster/encrypt-data/).
 {{< /note >}}
+
+{{% capture whatsnext %}}
+
+{{% /capture %}}

content/en/docs/concepts/configuration/taint-and-toleration.md

@@ -4,9 +4,13 @@ reviewers:
 - kevin-wangzefeng
 - bsalamat
 title: Taints and Tolerations
+content_template: templates/concept
 weight: 40
 ---
 
+{{< toc >}}
+
+{{% capture overview %}}
 Node affinity, described [here](/docs/concepts/configuration/assign-pod-node/#node-affinity-beta-feature),
 is a property of *pods* that *attracts* them to a set of nodes (either as a
 preference or a hard requirement). Taints are the opposite -- they allow a
@@ -18,7 +22,9 @@ marks that the node should not accept any pods that do not tolerate the taints.
 Tolerations are applied to pods, and allow (but do not require) the pods to schedule
 onto nodes with matching taints.
 
-{{< toc >}}
+{{% /capture %}}
+
+{{% capture body %}}
 
 ## Concepts
 
@@ -279,3 +285,9 @@ To make sure that turning on this feature doesn't break DaemonSets, starting in
 
 The above settings ensure backward compatibility, but we understand they may not fit all user's needs, which is why
 cluster admin may choose to add arbitrary tolerations to DaemonSets.
+
+{{% /capture %}}
+
+{{% capture whatsnext %}}
+
+{{% /capture %}}