move ToC headings section to markdown plugin

Author: thescientist13

src/pages/docs/content-as-data/pages-data.md

@@ -54,66 +54,6 @@ This is the data you would get back:
 }
 ```
 
-## Table of Contents
-
-Additionally for markdown pages, you can add a frontmatter property called `tocHeading` that will read all the HTML heading tags that match that number, and provide that as a subset of the data object. This is most useful for generating the table of contents for a page.
-
-Taking our previous example, if we were to configure this for `<h2>` tags:
-
-<!-- prettier-ignore-start -->
-
-<app-ctc-block variant="snippet" heading="src/pages/blog/first-post.md">
-
-  ```md
-  ---
-  author: Project Evergreen
-  published: 2024-01-01
-  tocHeading: 2
-  ---
-
-  # First Post
-
-  This is my first post.
-
-  ## Overview
-
-  Lorum Ipsum
-
-  ## First Point
-
-  Something something...
-  ```
-
-</app-ctc-block>
-
-<!-- prettier-ignore-end -->
-
-We would get this additional content as data out:
-
-```json
-{
-  "id": "blog-first-post",
-  "title": "First Post",
-  "label": "First Post",
-  "route": "/blog/first-post/",
-  "data": {
-    "author": "Project Evergreen",
-    "published": "2024-01-01",
-    "tocHeading": 2,
-    "tableOfContents": [
-      {
-        "content": "Overview",
-        "slug": "overview"
-      },
-      {
-        "content": "First Point",
-        "slug": "first-point"
-      }
-    ]
-  }
-}
-```
-
 ## External Content
 
 Using our [Source plugin](/docs/reference/plugins-api/#source), just as you can get your content as data _out_ of Greenwood, so can you provide your own sources of content (as data) _to_ Greenwood. This is great for pulling content from a headless CMS, database, or anything else you can imagine!

src/pages/docs/plugins/markdown.md

@@ -6,7 +6,7 @@ tocHeading: 2
 
 # Markdown
 
-For authoring in markdown, Greenwood provides a plugin that you can install, which by default supports the [CommonMark](https://commonmark.org/help/) specification and uses [**unifiedjs**](https://unifiedjs.com/) as the markdown / content framework. See the [plugin's README](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/plugin-markdown) for additional information, like standalone usage.
+For authoring in markdown, Greenwood provides a plugin that you can install which by default supports the [CommonMark](https://commonmark.org/help/) specification and uses [**unifiedjs**](https://unifiedjs.com/) as the markdown / content framework. See the [plugin's README](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/plugin-markdown) for additional information, like standalone usage.
 
 ## Installation
 
@@ -351,6 +351,66 @@ You can also define any custom frontmatter property you want and that will be ma
 
 <!-- prettier-ignore-end -->
 
+## Table of Contents
+
+You can add a frontmatter property called `tocHeading` that will read all the HTML heading tags that match that number in your markdown, and provide that as a subset of the data object in your [pages data schema](/docs/content-as-data/pages-data/#schema). This is most useful for generating the table of contents for a page.
+
+For example:
+
+<!-- prettier-ignore-start -->
+
+<app-ctc-block variant="snippet" heading="src/pages/blog/first-post.md">
+
+  ```md
+  ---
+  author: Project Evergreen
+  published: 2024-01-01
+  tocHeading: 2
+  ---
+
+  # First Post
+
+  This is my first post.
+
+  ## Overview
+
+  Lorum Ipsum
+
+  ## First Point
+
+  Something something...
+  ```
+
+</app-ctc-block>
+
+<!-- prettier-ignore-end -->
+
+We would get this additional content as data:
+
+```json
+{
+  "id": "blog-first-post",
+  "title": "First Post",
+  "label": "First Post",
+  "route": "/blog/first-post/",
+  "data": {
+    "author": "Project Evergreen",
+    "published": "2024-01-01",
+    "tocHeading": 2,
+    "tableOfContents": [
+      {
+        "content": "Overview",
+        "slug": "overview"
+      },
+      {
+        "content": "First Point",
+        "slug": "first-point"
+      }
+    ]
+  }
+}
+```
+
 ## Active Frontmatter
 
 With [`activeContent`](/docs/reference/configuration/#active-content) enabled, any of these properties would be available in your HTML or markdown through Greenwood's [content as data features](/docs/content-as-data/).