add en pages

content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md

@@ -3,11 +3,11 @@ title: Running Automated Tasks with a CronJob
 min-kubernetes-server-version: v1.8
 reviewers:
 - chenopis
-content_template: templates/task
+content_type: task
 weight: 10
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 You can use a {{< glossary_tooltip text="CronJob" term_id="cronjob" >}} to run {{< glossary_tooltip text="Jobs" term_id="job" >}} on a time-based schedule.
 These automated jobs run like [Cron](https://en.wikipedia.org/wiki/Cron) tasks on a Linux or UNIX system.
@@ -21,15 +21,16 @@ Therefore, jobs should be idempotent.
 
 For more limitations, see [CronJobs](/docs/concepts/workloads/controllers/cron-jobs).
 
-{{% /capture %}}
 
-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 
 * {{< include "task-tutorial-prereqs.md" >}}
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Creating a Cron Job
 
@@ -207,4 +208,4 @@ The `.spec.successfulJobsHistoryLimit` and `.spec.failedJobsHistoryLimit` fields
 These fields specify how many completed and failed jobs should be kept.
 By default, they are set to 3 and 1 respectively.  Setting a limit to `0` corresponds to keeping none of the corresponding kind of jobs after they finish.
 
-{{% /capture %}}
+

content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md

@@ -1,12 +1,12 @@
 ---
 title: Coarse Parallel Processing Using a Work Queue
 min-kubernetes-server-version: v1.8
-content_template: templates/task
+content_type: task
 weight: 30
 ---
 
 
-{{% capture overview %}}
+<!-- overview -->
 
 In this example, we will run a Kubernetes Job with multiple parallel
 worker processes.
@@ -23,19 +23,20 @@ Here is an overview of the steps in this example:
 1. **Start a Job that works on tasks from the queue**.  The Job starts several pods.  Each pod takes
   one task from the message queue, processes it, and repeats until the end of the queue is reached.
 
-{{% /capture %}}
 
 
-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 
 Be familiar with the basic,
 non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
 
 {{< include "task-tutorial-prereqs.md" >}}
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Starting a message queue service
 
@@ -292,9 +293,9 @@ Events:
 
 All our pods succeeded.  Yay.
 
-{{% /capture %}}
 
-{{% capture discussion %}}
+
+<!-- discussion -->
 
 ## Alternatives
 
@@ -331,4 +332,4 @@ exits with success, or if the node crashes before the kubelet is able to post th
 back to the api-server, then the Job will not appear to be complete, even though all items
 in the queue have been processed.
 
-{{% /capture %}}
+

content/en/docs/tasks/job/fine-parallel-processing-work-queue.md

@@ -1,11 +1,11 @@
 ---
 title: Fine Parallel Processing Using a Work Queue
-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: v1.8
 weight: 40
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 In this example, we will run a Kubernetes Job with multiple parallel
 worker processes in a given pod.
@@ -25,23 +25,24 @@ Here is an overview of the steps in this example:
 1. **Start a Job that works on tasks from the queue**.  The Job starts several pods.  Each pod takes
   one task from the message queue, processes it, and repeats until the end of the queue is reached.
 
-{{% /capture %}}
 
 
-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 
 {{< include "task-tutorial-prereqs.md" >}}
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 Be familiar with the basic,
 non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
 
-{{% /capture %}}
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Starting Redis
 
@@ -226,9 +227,9 @@ Working on lemon
 
 As you can see, one of our pods worked on several work units.
 
-{{% /capture %}}
 
-{{% capture discussion %}}
+
+<!-- discussion -->
 
 ## Alternatives
 
@@ -240,4 +241,4 @@ consider running your background workers with a `ReplicaSet` instead,
 and consider running a background processing library such as
 [https://github.com/resque/resque](https://github.com/resque/resque).
 
-{{% /capture %}}
+

content/en/docs/tasks/job/parallel-processing-expansion.md

@@ -1,11 +1,11 @@
 ---
 title: Parallel Processing using Expansions
-content_template: templates/task
+content_type: task
 min-kubernetes-server-version: v1.8
 weight: 20
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 This task demonstrates running multiple {{< glossary_tooltip text="Jobs" term_id="job" >}}
 based on a common template. You can use this approach to process batches of work in
@@ -16,9 +16,10 @@ The sample Jobs process each item simply by printing a string then pausing.
 
 See [using Jobs in real workloads](#using-jobs-in-real-workloads) to learn about how
 this pattern fits more realistic use cases.
-{{% /capture %}}
 
-{{% capture prerequisites %}}
+
+## {{% heading "prerequisites" %}}
+
 
 You should be familiar with the basic,
 non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
@@ -35,10 +36,10 @@ Once you have Python set up, you can install Jinja2 by running:
 ```shell
 pip install --user jinja2
 ```
-{{% /capture %}}
 
 
-{{% capture steps %}}
+
+<!-- steps -->
 
 ## Create Jobs based on a template
 
@@ -252,8 +253,8 @@ Kubernetes accepts and runs the Jobs you created.
 kubectl delete job -l jobgroup=jobexample
 ```
 
-{{% /capture %}}
-{{% capture discussion %}}
+
+<!-- discussion -->
 
 ## Using Jobs in real workloads
 
@@ -310,4 +311,4 @@ objects.
 
 You could also consider writing your own [controller](/docs/concepts/architecture/controller/)
 to manage Job objects automatically.
-{{% /capture %}}
+