Add TOC links.

.markdownlint.yaml

@@ -9,3 +9,6 @@ MD026:
 
 # Allow inline HTML (mostly to allow <a> tags on headings).
 MD033: false
+
+# Don't complain about the file not starting with a heading, because we put a TOC link at the top of each page.
+MD041: false

README.md

@@ -49,7 +49,7 @@ They represent my personal interpretation and explanation of the standard.
 
 I've just started writing these tutorials. I'll remove this notice when I think there's enough information to be useful.
 
-## Table of contents
+## <a id="contents"></a>Table of contents
 
 - [Introduction](docs/1-Introduction.md)
   - [What is SARIF?](docs/1-Introduction.md#what-is-sarif)

docs/1-Introduction.md

@@ -1,3 +1,5 @@
+[Table of contents](../README.md#contents)
+
 # Introduction
 
 ## <a id="what-is-sarif"></a>What is SARIF?
@@ -198,3 +200,5 @@ but not yet by OASIS as a whole.
 is called a <a href="Glossary.md#dynamic-analysis-tool">_dynamic analysis tool_</a>.
 SARIF does not claim to represent the output of dynamic analysis tools,
 but there are dynamic analysis tools that have adopted it successfully. YMMV.
+
+[Table of contents](../README.md#contents)

docs/2-Basics.md

@@ -1,3 +1,5 @@
+[Table of contents](../README.md#contents)
+
 # The Basics
 
 ## <a id="logs-runs"></a>Logs and runs
@@ -200,4 +202,6 @@ and
 <a id="note-7"></a>7. Again, see
 [§3.27.10, level property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012604)
 and
-[§3.27.9, kind property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012603).
+[§3.27.9, kind property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012603).
+
+[Table of contents](../README.md#contents)

docs/5.2-Resources.md

@@ -1,3 +1,5 @@
+[Table of contents](../README.md#contents)
+
 # Resources
 
 - The [SARIF Home Page](http://sarifweb.azurewebsites.net/) might be the only resource you need.
@@ -12,3 +14,5 @@ if it conforms to the spec.<sup><a href="#note-7">7</a></sup>
 a dozen checks for constraints that are present in the spec but not expressed in the schema.
 The spec has hundreds of such requirements ("**SHALL**" statements) and recommendations ("**SHOULD**" statements),
 so there's plenty of room to improve the validator.
+
+[Table of contents](../README.md#contents)