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

content/en/docs/concepts/services-networking/connect-applications-service.md

@@ -4,11 +4,14 @@ reviewers:
 - lavalamp
 - thockin
 title: Connecting Applications with Services
+content_template: templates/concept
 weight: 30
 ---
 
 {{< toc >}}
 
+{{% capture overview %}}
+
 ## The Kubernetes model for connecting containers
 
 Now that you have a continuously running, replicated application you can expose it on a network. Before discussing the Kubernetes approach to networking, it is worthwhile to contrast it with the "normal" way networking works with Docker.
@@ -19,6 +22,10 @@ Coordinating ports across multiple developers is very difficult to do at scale a
 
 This guide uses a simple nginx server to demonstrate proof of concept. The same principles are embodied in a more complete [Jenkins CI application](http://blog.kubernetes.io/2015/07/strong-simple-ssl-for-kubernetes.html).
 
+{{% /capture %}}
+
+{{% capture body %}}
+
 ## Exposing pods to the cluster
 
 We did this in a previous example, but let's do it once again and focus on the networking perspective. Create an nginx pod, and note that it has a container port specification:
@@ -319,10 +326,15 @@ LoadBalancer Ingress:   a320587ffd19711e5a37606cf4a74574-1142138393.us-east-1.el
 ...
 ```
 
-## Further reading
+{{% /capture %}}
+
+{{% capture whatsnext %}}
 
 Kubernetes also supports Federated Services, which can span multiple
 clusters and cloud providers, to provide increased availability,
 better fault tolerance and greater scalability for your services. See
 the [Federated Services User Guide](/docs/concepts/cluster-administration/federation-service-discovery/)
 for further information.
+
+{{% /capture %}}
+