Add RFC navigation elements

rfc/4/comments/index.md

@@ -0,0 +1,9 @@
+# Comments
+
+Additional comments of RFC-4:
+
+```{toctree}
+:maxdepth: 1
+:glob:
+*/index
+```

rfc/4/index.md

@@ -1,6 +1,16 @@
-# RFC: Axis Anatomical Orientation
+# RFC-4: Axis Anatomical Orientation
+
+```{toctree}
+:hidden:
+:maxdepth: 1
+templates/index
+reviews/index
+comments/index
+responses/index
+versions/index
+```
 
-Summary: An optional, explicit field for specification of maging axis-aligned anatomical orientation for bipeds or quadrupeds.
+Summary: An optional, explicit field for specification of imaging axis-aligned anatomical orientation for bipeds or quadrupeds.
 
 ## Status
 
@@ -304,13 +314,6 @@ Testing will include validating the presence and correctness of the `anatomicalO
 
 End-user applications SHOULD display the encoded information with, for example, the human-readable names of the axes along the rendered axes of the image or an orientation widget with a thumbnail of a person.
 
-## Tutorials and Examples (Optional Header)
-
-TODO
-
-Note: This document is based on the [RFC template from Hashicorp][template]
-(TODO: license requested).
-
 [IETF RFC 2119]: https://tools.ietf.org/html/rfc2119
 [rubber duck debugging]: https://en.wikipedia.org/wiki/Rubber_duck_debugging
-[template]: https://works.hashicorp.com/articles/rfc-template
+[template]: https://works.hashicorp.com/articles/rfc-template

rfc/4/markdown/Orientation.md

@@ -1,3 +1,6 @@
+---
+orphan: true
+---
 
 # Enum: Orientation
 

rfc/4/responses/index.md

@@ -0,0 +1,9 @@
+# Responses
+
+Responses from the authors of RFC-4:
+
+```{toctree}
+:maxdepth: 1
+:glob:
+*/index
+```

rfc/4/reviews/index.md

@@ -0,0 +1,9 @@
+# Reviews
+
+Reviews of RFC-4:
+
+```{toctree}
+:maxdepth: 1
+:glob:
+*/index
+```

rfc/4/versions/index.md

@@ -0,0 +1,9 @@
+# Versions
+
+Key versions of the RFC which have been sent for review, etc.
+
+```{toctree}
+:maxdepth: 1
+:glob:
+*/index
+```