/about/contribute/creating-and-editing-pages/index.md

[SataQiu]

Source File: /about/contribute/creating-and-editing-pages/index.md
Diff:

 diff --git a/content/en/about/contribute/creating-and-editing-pages/index.md b/content/en/about/contribute/creating-and-editing-pages/index.md
index 3d2d0243..4d83070b 100644
--- a/content/en/about/contribute/creating-and-editing-pages/index.md
+++ b/content/en/about/contribute/creating-and-editing-pages/index.md
@@ -62,22 +62,16 @@ is the best fit for your content:
   <tr>
     <td>Blog Post</td>
     <td>
-      A blog post is an article on Istio or products and technologies related to it. Typically, posts fall in one of the following three categories:
+      A blog post is a timely article on Istio or products and technologies related to it. Typically, posts fall in one of the following four categories:
       <ul>
       <li>Posts detailing the author’s experience using and configuring Istio, especially those that articulate a novel experience or perspective.</li>
-      <li>Posts highlighting Istio features.</li>
+      <li>Posts highlighting or announcing Istio features.</li>
+      <li>Posts announcing an Istio-related event.</li>
       <li>Posts detailing how to accomplish a task or fulfill a specific use case using Istio. Unlike Tasks and Examples, the technical accuracy of blog posts is not maintained and tested after publication.</li>
       </ul>
     </td>
   </tr>
 
-  <tr>
-    <td>News Entry</td>
-    <td>
-      A news entry post is a timely article on Istio and events related to it. News entries typically announce new releases or upcoming events.
-    </td>
-  </tr>
-
   <tr>
     <td>FAQ</td>
     <td>
@@ -136,25 +130,17 @@ The available front matter fields are:
 |`skip_byline`      | Set this to true to prevent the page from having a byline under the main title
 |`skip_seealso`     | Set this to true to prevent the page from having a "See also" section generated for it
 |`force_inline_toc` | Set this to true to force the generated table of contents to be inserted inline in the text instead of in a sidebar
-
-A few front-matter fields are specific to section pages (i.e. for files names `_index.md`):
-
-|Field                 | Description
-|----------------------|------------
-|`skip_list`           | Set this to true to prevent the auto-generated content on a section page
-|`simple_list`         | Set this to true to use a simple list layout rather than gallery layout for the auto-generated content of a section page
-|`list_below`          | Set this to true to insert the auto-generated content on a section page below the manually-written content
-|`list_by_publishdate` | Set this to true to sort the generated content on the page in order in publication date, rather than by page weight
+|`simple_list`      | Set this to true to force a generated section page to use a simple list layout rather that a gallery layout
+|`content_above`    | Set this to true to force the content portion of a section index to be rendered above the auto-generated part
 
 There are a few more front matter fields available specifically for blog posts:
 
-|Field           | Description
-|----------------|------------
-|`publishdate`   | Date of the post's original publication
-|`last_update`   | Date when the post last received a major revision
-|`attribution`   | Optional name of the post's author
-|`twitter`       | Optional Twitter handle of the post's author
-|`target_release`| Release this blog is written with in mind (this is normally the current major Istio release at the time the blog is authored or updated)
+|Field          | Description
+|---------------|------------
+|`publishdate`  | Date of the post's original publication
+|`last_update`  | Date when the post last received a major revision
+|`attribution`  | Optional name of the post's author
+|`twitter`      | Optional Twitter handle of the post's author
 
 ## Adding images
 
@@ -415,7 +401,6 @@ The available attributes are:
 |`downloadas`  | The default file name used when the user [downloads the preformatted block](#download-name).
 |`expandlinks` | Whether or not to expand [GitHub file references](#links-to-github-files) in the preformatted block.
 |`snippet`     | The name of the [snippet](#snippets) of content to extract from the preformatted block.
-|`repo`        | The repo to use for [GitHub links](#links-to-github-files) embedded in preformatted blocks.
 
 ### Inline vs. imported content
 
@@ -482,21 +467,6 @@ Which renders as:
 $ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-v3.yaml@
 {{< /text >}}
 
-Normally, links will point to the current release branch of the `istio/istio` repo. If you'd like a link
-that points to a different Istio repo instead, you can use the `repo` attribute:
-
-{{< text markdown >}}
-{{</* text syntax="bash" repo="operator" */>}}
-$ cat @README.md@
-{{</* /text */>}}
-{{< /text >}}
-
-which renders as:
-
-{{< text syntax="bash" repo="operator" >}}
-$ cat @README.md@
-{{< /text >}}
-
 If your preformatted content happens to use @ symbols for something else, you can turn off link expansion using the
 `expandlinks` attribute:
 
@@ -525,16 +495,9 @@ which renders as:
 
 {{< text_import file="test/snippet_example.txt" syntax="plain" snippet="SNIP1" >}}
 
-Within a text file, snippets can indicate the syntax of the snippet content and, for bash syntax, can
-include the syntax of the output. For example:
-
-{{< text plain >}}
-$snippet MySnippetFile.txt syntax="bash" outputis="json"
-{{< /text >}}
-
 ## Glossary terms
 
-When first introducing a specialized Istio term in a page, it is desirable to annotate the term as being in the glossary. This
+When first introducing a specialized Istio term in a page, it is desirable to annotate the terms as being in the glossary. This
 will produce special rendering inviting the user to click on the term in order to get a pop-up with the definition.
 
 {{< text markdown >}}

[vflong]

/accept

[mesher-bot]

Thank you @vflong, this issue had been assigned to you.

[vflong]

/pushed

[rootsongjc]

/merged