HTCondorWiki: Read The Docs

-{section: Overview}
+{section: Read the Docs Overview}
 
 In 2019 we migrated the HTCondor Manual from our old LaTeX format into the Sphinx documentation generator using the reStructuredText format. We will also be hosting it on Read the Docs. The manual can be found here:
 
@@ -84,7 +84,67 @@
 
 This section provides some markup style guidelines, as well as information about how we use both built-in and custom tools.
 
+{subsection: Section Titles}
 
+Section titles are very fluid in rST and there are many different ways to make them. To keep things as consistent as possible, please use the following:
+
+{code}
+Page titles get underlined with the = symbol
+============================================
+
+Section titles get underlined with the - symbol
+-----------------------------------------------
+
+Subsection titles get underlined with the ' symbol
+''''''''''''''''''''''''''''''''''''''''''''''''''
+{endcode}
+
+{subsection: Indentation}
+
+The rST format is very sensitive to indentation. Paragraphs and other blocks of text are expected to be left-aligned. Indenting a block by any amount of whitespace (compared to the preceding block) causes it to get indented.
+
+{code}
+This is a top-level block of text. It will appear aligned to the left-most side of the page.
+
+ This paragraph is indented by one space. Even though it's only a single space,
+ it will render as a full first-level indent.
+
+  This paragraph is indented by one more space than the one above it. As a
+  result it will render as a second-level indent.
+
+    This time I've indented a block by two more spaces the one above it. It
+    doesn't matter that this is inconsistent with the single-space indents
+    above. This block will render as a third-level indent.
+
+Back to the top level!
+
+            This block is indented by 12 spaces. However, as with the previous
+            examples, the amount of whitespace doesn't matter. Because it's the
+            first indented block compared to the preceding block, it will only
+            render as a first-level indent.
+{endcode}
+
+{subsection: Linking to gittrac tickets}
+
+Use the following syntax to automatically link to a gittrac ticket, where #### is the number of the ticket:
+
+{code}
+:ticket:`####`
+{endcode}
+
+{subsection: Adding index entries}
+
+To add a basic index entry, use the following syntax:
+
+{code}
+:index:`Name of index entry`
+{endcode}
+
+If you want your index entry to appear under a parent entry, the syntax is a little more complicated:
+
+{code}
+:index:`Name of index entry <single: Name of index entry; Name of parent entry>`
+{endcode}
 
 {section: Publishing}