add en pages

content/en/docs/contribute/new-content/blogs-case-studies.md

@@ -2,19 +2,19 @@
 title: Submitting blog posts and case studies
 linktitle: Blogs and case studies
 slug: blogs-case-studies
-content_template: templates/concept
+content_type: concept
 weight: 30
 ---
 
 
-{{% capture overview %}}
+<!-- overview -->
 
 Anyone can write a blog post and submit it for review.
 Case studies require extensive review before they're approved.
 
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 
 ## Write a blog post
 
@@ -52,8 +52,9 @@ Have a look at the source for the
 
 Refer to the [case study guidelines](https://github.com/cncf/foundation/blob/master/case-study-guidelines.md) and submit your request as outlined in the guidelines. 
 
-{{% /capture %}}
 
-{{% capture whatsnext %}}
 
-{{% /capture %}}
+## {{% heading "whatsnext" %}}
+
+
+

content/en/docs/contribute/new-content/new-features.md

@@ -1,7 +1,7 @@
 ---
 title:  Documenting a feature for a release
 linktitle: Documenting for a release
-content_template: templates/concept
+content_type: concept
 main_menu: true
 weight: 20
 card:
@@ -9,7 +9,7 @@ card:
   weight: 45
   title:  Documenting a feature for a release
 ---
-{{% capture overview %}}
+<!-- overview -->
 
 Each major Kubernetes release introduces new features that require documentation. New releases also bring updates to existing features and documentation (such as upgrading a feature from alpha to beta).
 
@@ -19,9 +19,9 @@ feature as a pull request to the appropriate development branch of the
 editorial feedback or edits the draft directly. This section covers the branching
 conventions and process used during a release by both groups.
 
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 
 ## For documentation contributors
 
@@ -131,4 +131,3 @@ add it to [Alpha/Beta Feature gates](/docs/reference/command-line-tools-referenc
 as part of your pull request. If your feature is moving out of Alpha, make sure to
 remove it from that table.
 
-{{% /capture %}}

content/en/docs/contribute/new-content/open-a-pr.md

@@ -1,14 +1,14 @@
 ---
 title: Opening a pull request
 slug: new-content
-content_template: templates/concept
+content_type: concept
 weight: 10
 card:
   name: contribute
   weight: 40
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 {{< note >}}
 **Code developers**: If you are documenting a new feature for an
@@ -22,9 +22,9 @@ If your change is small, or you're unfamiliar with git, read [Changes using GitH
 
 If your changes are large, read [Work from a local fork](#fork-the-repo) to learn how to make changes locally on your computer.
 
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 
 ## Changes using GitHub
 
@@ -475,10 +475,11 @@ Most repositories use issue and PR templates. Have a look through some open
 issues and PRs to get a feel for that team's processes. Make sure to fill out
 the templates with as much detail as possible when you file issues or PRs.
 
-{{% /capture %}}
 
-{{% capture whatsnext %}}
+
+## {{% heading "whatsnext" %}}
+
 
 - Read [Reviewing](/docs/contribute/reviewing/revewing-prs) to learn more about the review process.
 
-{{% /capture %}}
+

content/en/docs/contribute/new-content/overview.md

@@ -1,19 +1,19 @@
 ---
 title: Contributing new content overview
 linktitle: Overview
-content_template: templates/concept
+content_type: concept
 main_menu: true
 weight: 5
 ---
 
-{{% capture overview %}}
+<!-- overview -->
 
 This section contains information you should know before contributing new content.
 
 
-{{% /capture %}}
 
-{{% capture body %}}
+
+<!-- body -->
 
 ## Contributing basics
 
@@ -58,4 +58,4 @@ Limit pull requests to one language per PR. If you need to make an identical cha
 
 The [doc contributors tools](https://github.com/kubernetes/website/tree/master/content/en/docs/doc-contributor-tools) directory in the `kubernetes/website` repository contains tools to help your contribution journey go more smoothly.
 
-{{% /capture %}}
+