docs: Move and update pages from the manual

docs/adapting-existing.md

@@ -1,4 +1,12 @@
+---
+nav_order: 6
+---
+
 # Adapting existing mainstream distributions
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## System layout
 

docs/atomic-upgrades.md

@@ -1,4 +1,12 @@
+---
+nav_order: 5
+---
+
 # Atomic Upgrades
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## You can turn off the power anytime you want...
 

docs/buildsystem-and-repos.md

@@ -1,4 +1,12 @@
+---
+nav_order: 8
+---
+
 # Writing a buildsystem and managing repositories
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 OSTree is not a package system.  It does not directly support building
 source code.  Rather, it is a tool for transporting and managing

docs/deployment.md

@@ -1,4 +1,12 @@
+---
+nav_order: 4
+---
+
 # Deployments
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## Overview
 

docs/formats.md

@@ -1,4 +1,12 @@
+---
+nav_order: 7
+---
+
 # OSTree data formats
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## On the topic of "smart servers"
 

docs/introduction.md

@@ -1,4 +1,12 @@
+---
+nav_order: 2
+---
+
 # OSTree Overview
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## Introduction
 

docs/related-projects.md

@@ -1,4 +1,12 @@
+---
+nav_order: 10
+---
+
 # Related Projects
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 OSTree is in many ways very evolutionary.  It builds on concepts and
 ideas introduced from many different projects such as

docs/repo.md

@@ -1,4 +1,12 @@
+---
+nav_order: 3
+---
+
 # Anatomy of an OSTree repository
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 ## Core object types and data model
 

docs/repository-management.md

@@ -1,4 +1,12 @@
+---
+nav_order: 9
+---
+
 # Managing content in OSTree repositories
+{: .no_toc }
+
+1. TOC
+{:toc}
 
 Once you have a build system going, if you actually want client
 systems to retrieve the content, you will quickly feel a need for