removing toc shortcode. (#10720)

This commit is contained in:
MengZeLee
2018-10-26 02:02:31 +08:00
committed by k8s-ci-robot
parent 8f2bb3d6ad
commit 04163e9a7c
81 changed files with 183 additions and 289 deletions
@@ -20,7 +20,6 @@ We encourage you to add new [localizations](https://blog.mozilla.org/l10n/2011/
{{% /capture %}}
{{< toc >}}
{{% capture body %}}
@@ -4,7 +4,6 @@ content_template: templates/concept
weight: 40
---
{{< toc >}}
{{% capture overview %}}
@@ -62,7 +61,7 @@ linkTitle: Title used in links
### Documentation Side Menu
The documentation side-bar menu is built from the _current section tree_ starting below `docs/`.
The documentation side-bar menu is built from the _current section tree_ starting below `docs/`.
It will show all sections and their pages.
@@ -86,7 +85,7 @@ toc_hide: true
### The Main Menu
The site links in the top-right menu -- and also in the footer -- are built by page-lookups. This is to make sure that the page actually exists. So, if the `case-studies` section does not exist in a site (language), it will not be linked to.
The site links in the top-right menu -- and also in the footer -- are built by page-lookups. This is to make sure that the page actually exists. So, if the `case-studies` section does not exist in a site (language), it will not be linked to.
## Page Bundles
@@ -137,4 +136,3 @@ The `SASS` source of the stylesheets for this site is stored below `src/sass` an
* [Style guide](/docs/contribute/style/style-guide)
{{% /capture %}}
@@ -23,7 +23,6 @@ template to use for a new topic, start with the
{{% /capture %}}
{{< toc >}}
{{% capture body %}}
@@ -51,18 +50,18 @@ To write a new concept page, create a Markdown file in a subdirectory of the
The page's body will look like this (remove any optional captures you don't
need):
```
{{%/* capture overview */%}}
{{%/* /capture */%}}
{{%/* capture body */%}}
{{%/* /capture */%}}
{{%/* capture whatsnext */%}}
{{%/* /capture */%}}
```
@@ -101,28 +100,28 @@ To write a new task page, create a Markdown file in a subdirectory of the
The page's body will look like this (remove any optional captures you don't
need):
```
{{%/* capture overview */%}}
{{%/* /capture */%}}
{{%/* capture prerequisites */%}}
{{</* include "task-tutorial-prereqs.md" */>}} {{</* version-check */>}}
{{%/* /capture */%}}
{{%/* capture steps */%}}
{{%/* /capture */%}}
{{%/* capture discussion */%}}
{{%/* /capture */%}}
{{%/* capture whatsnext */%}}
{{%/* /capture */%}}
```
@@ -167,32 +166,32 @@ To write a new tutorial page, create a Markdown file in a subdirectory of the
The page's body will look like this (remove any optional captures you don't
need):
```
{{%/* capture overview */%}}
{{%/* /capture */%}}
{{%/* capture prerequisites */%}}
{{</* include "task-tutorial-prereqs.md" */>}} {{</* version-check */>}}
{{%/* /capture */%}}
{{%/* capture objectives */%}}
{{%/* /capture */%}}
{{%/* capture lessoncontent */%}}
{{%/* /capture */%}}
{{%/* capture cleanup */%}}
{{%/* /capture */%}}
{{%/* capture whatsnext */%}}
{{%/* /capture */%}}
```
@@ -221,4 +220,3 @@ An example of a published topic that uses the tutorial template is
- Learn about [content organization](/docs/contribute/style/content-organization/)
{{% /capture %}}