(GH-1932) Initial ordering of top level pages

More work is needed here, but this makes the top level pages match the
order that is in the current documentation.

Author: gep13

docs/input/docs/build-server-support/index.cshtml

@@ -0,0 +1,7 @@
+---
+Order: 30
+Description: Need to put something here...
+---
+<p>@Html.Raw(Model.String(DocsKeys.Description))</p>
+
+@Html.Partial("_ChildPages")

docs/input/docs/configuration.md

@@ -1,3 +1,8 @@
+---
+Order: 20
+Title: Configuration
+---
+
 # Configuration
 GitVersion 3.0 is mainly powered by configuration and no longer has branching
 strategies hard coded.
@@ -306,7 +311,7 @@ By looking at this graph, you cannot tell which of these scenarios happened:
 
 2. release/1.0.0 branches off feature/foo
    - Branch feature/foo from master
-   - Branch release/1.0.0 from feature/foo 
+   - Branch release/1.0.0 from feature/foo
    - Add a commit to both release/1.0.0 and feature/foo
    - feature/foo is the base for release/1.0.0
 

docs/input/docs/examples.md

@@ -1,3 +1,8 @@
+---
+Order: 40
+Title: Examples
+---
+
 # Examples
 ![README](img/CommitGraph.png)
 

docs/input/docs/faq.md

@@ -1,3 +1,8 @@
+---
+Order: 50
+Title: FAQ
+---
+
 # FAQ
 
 ## Why is my version not incrementing?

docs/input/docs/git-branching-strategies/index.cshtml

@@ -0,0 +1,7 @@
+---
+Order: 90
+Description: Need to put something here...
+---
+<p>@Html.Raw(Model.String(DocsKeys.Description))</p>
+
+@Html.Partial("_ChildPages")

docs/input/docs/git-branching-strategies/index.md renamed to docs/input/docs/git-branching-strategies/overview.md

@@ -0,0 +1,7 @@
+---
+Order: 80
+Description: Need to put something here...
+---
+<p>@Html.Raw(Model.String(DocsKeys.Description))</p>
+
+@Html.Partial("_ChildPages")

docs/input/docs/more-info/index.cshtml

@@ -0,0 +1,7 @@
+---
+Order: 100
+Description: Need to put something here...
+---
+<p>@Html.Raw(Model.String(DocsKeys.Description))</p>
+
+@Html.Partial("_ChildPages")

docs/input/docs/reference/index.cshtml

@@ -0,0 +1,7 @@
+---
+Order: 10
+Description: Need to put something here...
+---
+<p>@Html.Raw(Model.String(DocsKeys.Description))</p>
+
+@Html.Partial("_ChildPages")

docs/input/docs/usage/index.cshtml

@@ -1,3 +1,8 @@
+---
+Order: 70
+Title: Who is using GitVersion
+---
+
 # Who is using GitVersion
 Various people are actively using GitVersion, and taking advantage of the automatic generation of their version numbers.  Here is a list of applications that we know about today.
 

docs/input/docs/who.md

@@ -1,3 +1,8 @@
+---
+Order: 60
+Title: Why?
+---
+
 # Why use GitVersion
 GitVersion makes versioning woes a thing of the past. It looks at your git history to calculate what the version currently is. I have seen and used many different approaches in the past, all have downfalls and often are not transportable between projects.