1 files changed, 36 insertions, 0 deletions
diff --git a/content/content/table-of-contents.md b/content/content/table-of-contents.md
new file mode 100644
index 0000000..d541d86
--- /dev/null
+++ b/content/content/table-of-contents.md
@@ -0,0 +1,36 @@
++++
+title = "Table of Contents"
+weight = 60
++++
+
+Each page/section will automatically generate a table of contents for itself based on the headers generated with markdown.
+
+It is available in the template through the `page.toc` or `section.toc` variable.
+You can view the [template variables](@/templates/pages-sections.md#table-of-contents)
+documentation for information on its structure.
+
+Here is an example of using that field to render a two-level table of contents:
+
+```jinja2
+<ul>
+{% for h1 in page.toc %}
+    <li>
+        <a href="{{h1.permalink | safe}}">{{ h1.title }}</a>
+        {% if h1.children %}
+            <ul>
+                {% for h2 in h1.children %}
+                    <li>
+                        <a href="{{h2.permalink | safe}}">{{ h2.title }}</a>
+                    </li>
+                {% endfor %}
+            </ul>
+        {% endif %}
+    </li>
+{% endfor %}
+</ul>
+```
+
+While headers are neatly ordered in this example, it will work just as well with disjoint headers.
+
+Note that all existing HTML tags from the title will NOT be present in the table of contents to
+avoid various issues.