Restructure docs

site/building.md

@@ -1,6 +1,6 @@
 ---
 title: Building Weave Net
-layout: default
+menu_order: 160
 ---
 
 # Building Weave Net

site/encryption.md

@@ -1,6 +1,6 @@
 ---
 title: Encryption and Weave Net
-layout: default
+menu_order: 90
 ---
 
 

site/faq.md

@@ -1,6 +1,6 @@
 ---
 title: Weave Net FAQ
-layout: default
+menu_order: 140
 ---
 
 

site/fastdp.md

@@ -1,6 +1,6 @@
 ---
 title: Using Fast Datapath
-layout: default
+menu_order: 70
 ---
 
 

site/fastdp/fastdp-how-it-works.md

@@ -1,21 +1,21 @@
 ---
 title: How Fast Datapath Works
-layout: default
+menu_order: 10
 ---
 
 
 Weave Net implements an overlay network between Docker hosts. Without fast datapath enabled, each packet is encapsulated in a tunnel protocol header and sent to the destination host, where the header is removed.  The Weave router is a user space process, which means that the packet follows a winding path in and out of the Linux kernel:
 
-![Weave Net Encapsulation](/site/images/weave-net-encap1-1024x459.png)
+![Weave Net Encapsulation](weave-net-encap1-1024x459.png)
 
 
 The fast datapath in Weave Net uses the Linux kernel's [Open vSwitch datapath module](https://www.kernel.org/doc/Documentation/networking/openvswitch.txt). This module enables the Weave Net router to tell the kernel how to process packets:
 
-![Weave Net Encapsulation](/site/images/weave-net-fdp1-1024x454.png)
+![Weave Net Encapsulation](weave-net-fdp1-1024x454.png)
 
 Because Weave Net issues instructions directly to the kernel, context switches are decreased, and so by using `fast datapath` CPU overhead and latency is reduced. The packet goes straight from your application to the kernel, where the Virtual Extensible Lan (VXLAN) header is added (the NIC does this if it offers VXLAN acceleration). VXLAN is an IETF standard UDP-based tunneling protocol that enable you to use common networking tools like [Wireshark](https://www.wireshark.org/) to inspect the tunneled packets.
 
-![Weave Net Encapsulation](/site/images/weave-frame-encapsulation-178x300.png)
+![Weave Net Encapsulation](weave-frame-encapsulation-178x300.png)
 
 Prior to version 1.2, Weave Net used a custom encapsulation format. Fast datapath uses VXLAN, and like Weave Net's custom encapsulation format, VXLAN is UDP-based, and therefore needs no special configuration with network infrastructure. 
 

site/features.md

@@ -1,6 +1,6 @@
 ---
 title: Weave Features
-layout: default
+menu_order: 20
 ---
 
 The following is a comprehensive list and overview of all the features available in Weave 

site/installing-weave.md

@@ -1,6 +1,6 @@
 ---
 title: Installing Weave Net
-layout: default
+menu_order: 30
 ---
 
 
@@ -44,4 +44,4 @@ for the latest Weave AMIs and
  * [Troubleshooting](/site/troubleshooting.md)
  * [Building](/site/building.md)
  * [Using Weave with Systemd](/site/systemd.md)
- 
+ 

site/introducing-weave.md

@@ -1,6 +1,6 @@
 ---
 title: Introducing Weave Net
-layout: default
+menu_order: 10
 ---
 
 
@@ -15,7 +15,7 @@ Services provided by application containers on the weave network can be exposed
 
 Weave Net simplifies setting up a container network. Because containers on a Weave network use standard port numbers, (for example MySQL’s default is port 3306), managing microservices is straightforward. Every container can find the IP of any other container using a simple DNS query on the container's name, and it can also communicate directly without NAT, without using port mappings or complicated ambassador linking.  And best of all deploying a Weave container network requires zero changes to your application’s code. 
 
-![Weave Net Encapsulation](/site/images/weave-net-overview.png)
+![Weave Net Encapsulation](weave-net-overview.png)
 
 ###Service Discovery
 

site/ip-addresses.md

@@ -1,6 +1,6 @@
 ---
 title: IP Addresses, Routes and Networks
-layout: default
+menu_order: 50
 ---
 
 

site/ip-addresses/configuring-weave.md

@@ -1,6 +1,6 @@
 ---
 title: Configuring Weave to Explicitly Use an IP Range
-layout: default
+menu_order: 10
 ---
 
 The default configurations for both Weave Net and Docker use [Private

site/ipam.md

@@ -1,6 +1,6 @@
 ---
 title: Address Allocation with IP Address Management (IPAM)
-layout: default
+menu_order: 110
 ---
 
 

site/ipam/allocation-multi-ipam.md

@@ -1,6 +1,6 @@
 ---
 title: Automatic Allocation Across Multiple Subnets
-layout: default
+menu_order: 10
 ---
 
 

site/ipam/stop-remove-peers-ipam.md

@@ -1,6 +1,6 @@
 ---
 title: Starting, Stopping and Removing Peers
-layout: default
+menu_order: 20
 ---
 
 

site/ipam/troubleshooting-ipam.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting the IP Allocator
-layout: default
+menu_order: 30
 ---
 
 

site/plugin.md

@@ -1,6 +1,6 @@
 ---
 title: Using the Weave Net Docker Network Plugin
-layout: default
+menu_order: 80
 ---
 
 

site/router-topology.md

@@ -1,6 +1,7 @@
 ---
 title: How Weave Net Works
 layout: default
+menu_order: 100
 ---
 
 
@@ -43,7 +44,7 @@ changing topology. For example, in this network, peer 1 is connected
 directly to 2 and 3, but if 1 needs to send a packet to 4 or 5 it must
 first send it to peer 3:
 
-![A Partially Connected Weave Network](/site/images/top-diag1.png "Partially connected Weave Network")
+![A Partially Connected Weave Network](top-diag1.png "Partially connected Weave Network")
 
 **See Also**
 

site/router-topology/network-topology.md

@@ -1,6 +1,6 @@
 ---
 title: How Weave Net Interprets Network Topology
-layout: default
+menu_order: 20
 ---
 
 This section contains the following topics: 

site/router-topology/router-encapsulation.md

@@ -1,6 +1,6 @@
 ---
 title: Weave Net Router Encapsulation
-layout: default
+menu_order: 10
 ---
 
 
@@ -61,4 +61,4 @@ MAC discovery.
 
 **See Also**
 
- * [How Weave Net Inteprets Network Topology](/site/router-topology/network-topology.md)
+ * [How Weave Net Inteprets Network Topology](/site/router-topology/network-topology.md)

site/systemd.md

@@ -1,6 +1,6 @@
 ---
 title: Using Weave with Systemd
-layout: default
+menu_order: 130
 ---
 
 

site/troubleshooting.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting Weave Net
-layout: default
+menu_order: 150
 ---
 
 

site/using-weave.md

@@ -1,6 +1,6 @@
 ---
 title: Using Weave Net - Example
-layout: default
+menu_order: 40
 ---
 
 Weave Net provides a simple to deploy networking solution for containerized apps. The example described and built upon throughout this `Using Weave Net` section describes how to manage a Weave container network using a sample application which consists of two simple `netcat` services deployed to containers on two separate hosts, and sometimes extended across three hosts.  

site/using-weave/application-isolation.md

@@ -1,6 +1,6 @@
 ---
 title: Isolating Applications on a Weave Network
-layout: default
+menu_order: 30
 ---
 
 A single Weave network can host multiple, isolated applications where each application's containers are able 

site/using-weave/deploying-applications.md

@@ -1,6 +1,6 @@
 ---
 title: Deploying Applications To Weave Net
-layout: default
+menu_order: 10
 ---
 
 This section contains the following topics: 

site/using-weave/dynamically-attach-containers.md

@@ -1,6 +1,6 @@
 ---
 title: Dynamically Attaching and Detaching Applications
-layout: default
+menu_order: 40
 ---
 
 

site/using-weave/finding-adding-hosts-dynamically.md

@@ -1,6 +1,6 @@
 ---
 title: Adding and Removing Hosts Dynamically
-layout: default
+menu_order: 50
 ---
 
 

site/using-weave/host-network-integration.md

@@ -1,6 +1,6 @@
 ---
 title: Integrating a Host Network with Weave Net
-layout: default
+menu_order: 60
 ---
 
 Weave application networks can be integrated with an external host network, establishing connectivity between the host and with application containers running anywhere.

site/using-weave/manual-ip-address.md

@@ -1,6 +1,6 @@
 ---
 title: Manually Specifying the IP Address of a Container
-layout: default
+menu_order: 20
 ---
 
 Containers are automatically allocated an IP address that is unique across the Weave network. You can see which address was allocated by running, [`weave ps`](/site/troubleshooting.md#weave-status):

site/using-weave/multi-cloud-multi-hop.md

@@ -1,6 +1,6 @@
 ---
 title: Enabling Multi-Cloud, Multi-Hop Networking and Routing
-layout: default
+menu_order: 100
 ---
 
 

site/using-weave/security-untrusted-networks.md

@@ -1,6 +1,6 @@
 ---
 title: Securing Connections Across Untrusted Networks
-layout: default
+menu_order: 80
 ---
 
 

site/using-weave/service-export.md

@@ -1,6 +1,6 @@
 ---
 title: Exposing Services to the Outside World
-layout: default
+menu_order: 70
 ---
 
 Services running in containers on a Weave network can be made

site/using-weave/service-management.md

@@ -1,6 +1,6 @@
 ---
 title: Managing Services in Weave Net - Exporting, Importing, Binding and Routing
-layout: default
+menu_order: 90
 ---
 
 This section contains the following topics: 

site/weave-docker-api.md

@@ -1,6 +1,6 @@
 ---
 title: Setting Up The Weave Net Docker API Proxy
-layout: default
+menu_order: 60
 ---
 
 

site/weave-docker-api/automatic-discovery-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Using Automatic Discovery With the Weave Net Proxy
-layout: default
+menu_order: 30
 ---
 
 Containers launched via the proxy use [weaveDNS](/site/weavedns/overview-using-weavedns.md)

site/weave-docker-api/launching-without-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Launching Containers With Weave Run (without the Proxy)
-layout: default
+menu_order: 50
 ---
 
 

site/weave-docker-api/name-resolution-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Name resolution via `/etc/hosts`
-layout: default
+menu_order: 40
 ---
 
 

site/weave-docker-api/securing-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Securing the Docker Communications With TLS
-layout: default
+menu_order: 20
 ---
 
 If you are [connecting to the docker daemon with

site/weave-docker-api/troubleshooting-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting
-layout: default
+menu_order: 60
 ---
 
 The command

site/weave-docker-api/using-proxy.md

@@ -1,6 +1,6 @@
 ---
 title: Using The Weave Docker API Proxy
-layout: default
+menu_order: 10
 ---
 
 

site/weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: Using WeaveDNS
-layout: default
+menu_order: 120
 ---
 
 

site/weavedns/how-works-weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: How Weave Finds Containers
-layout: default
+menu_order: 10
 ---
 
 

site/weavedns/load-balance-fault-weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: Load Balancing and Fault Resilience with weaveDNS
-layout: default
+menu_order: 20
 ---
 
 

site/weavedns/managing-domains-weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: Managing Domains
-layout: default
+menu_order: 30
 ---
 
 The following topics are discussed:

site/weavedns/managing-entries-weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: Managing Domain Entries
-layout: default
+menu_order: 40
 ---
 
 

site/weavedns/troubleshooting-weavedns.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting and Present Limitations
-layout: default
+menu_order: 50
 ---