added all missing links to existing md files

fixed up all links and png refs in md files
added more toc files for navigation entries
fixed some issues with not converted links

Author: bethalha-havok

Assets/MixedRealityToolkit.Examples/toc.yml

@@ -0,0 +1,12 @@
+- name: Demos
+  href: Demos/README.md
+  items:
+  - name: Standard Shader
+    href: Demos/StandardShader/README.md
+- name: SDK
+  href: SDK/README.md
+  items:
+  - name: Basic Introduction
+    href: SDK/Example01-BasicIntroduction/README.md
+- name: Standard Assets
+  href: StandardAssets/README.md

Assets/MixedRealityToolkit.SDK/Features/UX/Scripts/Controllers/README.md

@@ -18,11 +18,11 @@ The framework is flexible enough to allow you to provide offsets to rotate and r
 
 Using the visualizer is extremely simple, just add it to an existing GameObject in your scene and provided you have configured your controller correctly, they will simply be instantiated into the scene at runtime when controllers are detected.
 
-![](External/HowTo/ControlerVisualizer/ControllerVisualizerInspector.png)
+![](../../../../../../External/ReadMeImages/ControllerVisualizer/ControllerVisualizerInspector.png)
 
 Check the documentation on configuring Controller Profiles for more details:
 
-* [MixedReality Controller Configuration Profile configuration](Assets/MixedRealityToolkit-SDK/Profiles/MixedRealityControllerConfigurationProfile.md)
+* [MixedReality Controller Configuration Profile configuration](../../../../Profiles/MixedRealityControllerConfigurationProfile.md)
 
 ### Controller Visualizer notes
 

Assets/MixedRealityToolkit.SDK/Features/toc.yml

@@ -0,0 +1,11 @@
+- name: UX
+  href: UX/README.md
+  items:
+  - name: Interactable
+    href: UX/Interactable/README.md
+  - name: Prefabs
+    href: UX/Prefabs/README.md
+  - name: Script Controllers
+    href: UX/Scripts/Controllers/README.md
+  - name: Script Tooltips
+    href: UX/Scripts/Tooltips/README.md

Assets/MixedRealityToolkit.SDK/Profiles/MixedRealityControllerConfigurationProfile.md

@@ -2,15 +2,15 @@
 
 When you need to use input controllers for your Mixed Reality project, they are registered and configured centrally within the Controller configuration profile as you can see here:
 
-![](External/HowTo/ControllerConfigurationProfile/01-MixedRealityControllerConfigurationProfileInspector.png)
+![](../../../External/ReadMeImages/ControllerConfigurationProfile/01-MixedRealityControllerConfigurationProfileInspector.png)
 
 This enables you to very quickly define which SDK's / controllers you want to support in your project and configure how each are intended to work.
 
 The configuration is broken down in to several key components, as detailed below:
 
 ## Main Controller Template definition
 ---
-![](External/HowTo/ControllerConfigurationProfile/02-ControllerTemplateDefinition.png)
+![](../../../External/ReadMeImages/ControllerConfigurationProfile/02-ControllerTemplateDefinition.png)
 
 In the first section of the configuration, the options are detailed as follows:
 
@@ -34,7 +34,7 @@ This enables you to add a new controller definition (detailed below) to the prof
 
 ## Controller Template
 ---
-![](External/HowTo/ControllerConfigurationProfile/03-ControllerTemplate.png)
+![](../../../External/ReadMeImages/ControllerConfigurationProfile/03-ControllerTemplate.png)
 
 Each controller template allows you to configure any of the supported controllers for the various SDK's that have been enabled through the Mixed Reality Toolkit.
 Each controller is added by SDK and the prevailing hand.
@@ -84,7 +84,7 @@ These are different for each controller type, as shown below:
 
 | Motion Controller | Oculus Touch | Vive Wand |
 |---|---|---|
-|![](External/HowTo/ControllerConfigurationProfile/04-WMRInteractions.png)|![](External/HowTo/ControllerConfigurationProfile/05-OculusTouchInteractions.png)|![](External/HowTo/ControllerConfigurationProfile/06-ViveWandInteractions.png)|
+|![](../../../External/ReadMeImages/ControllerConfigurationProfile/04-WMRInteractions.png)|![](../../../External/ReadMeImages/ControllerConfigurationProfile/05-OculusTouchInteractions.png)|![](../../../External/ReadMeImages/ControllerConfigurationProfile/06-ViveWandInteractions.png)|
 
 > In the future custom mappings may become available, for now they are defined per the devices own specification according to the input definitions set out by Unity
 

Assets/MixedRealityToolkit.SDK/Profiles/toc.yml

@@ -0,0 +1,3 @@
+- name: Mixed Reality Controller Configuration Profile
+  href: MixedRealityControllerConfigurationProfile.md
+  

Assets/MixedRealityToolkit.SDK/StandardAssets/toc.yml

@@ -0,0 +1,12 @@
+- name: Audio
+  href: Audio/README.md
+- name: Fonts
+  href: Fonts/README.md
+- name: Materials
+  href: Materials/README.md
+- name: Models
+  href: Models/README.md
+- name: Shaders
+  href: Shaders/README.md
+- name: Textures
+  href: Textures/README.md

Assets/MixedRealityToolkit.SDK/toc.yml

@@ -0,0 +1,8 @@
+- name: Features
+  href: Features/toc.yml
+  homepage: Features/README.md
+- name: Profiles
+  href: Profiles/toc.yml
+  homepage: Profiles/README.md
+- name: Standard Assets
+  href: StandardAssets/toc.yml

Assets/MixedRealityToolkit/Definitions/README.md

@@ -65,20 +65,20 @@ For specific constructs, the following information details the relationships bet
 ### Controllers
 
 The controller definition relationships are defined as shown below:
-![](External/ReadMeImages/MRTK-ControllerDiagram.png)
+![](../../../External/ReadMeImages/MRTK-ControllerDiagram.png)
 
 ### Headsets
 
 The headset definition relationships are defined as shown below:
-![](External/ReadMeImages/MRTK-HeadsetDefinition.png)
+![](../../../External/ReadMeImages/MRTK-HeadsetDefinition.png)
 
 ### Internal MRTK InputActions
 
 Input Actions are those internal mapped actions available to the MRTK.  Each controller button would be dynamically mapped to an MRTK action for use in the SDK or output from the InputSystem.
 
 These are listed as follows:
-![](External/ReadMeImages/MRTK-InputActions.png)
+![](../../../External/ReadMeImages/MRTK-InputActions.png)
 
 ## Additional Information
 
-For additional information, please see the [MRTK vNext architecture outline](MRTK-vNext.md) and the [vNext SDK Outline](MRTK-SDK.md)
+For additional information, please see the [MRTK vNext architecture outline](../../../MRTK-vNext.md) and the [vNext SDK Outline](../../../MRTK-SDK.md)

Assets/MixedRealityToolkit/toc.yml

@@ -0,0 +1,17 @@
+- name: Definitions
+  href: Definitions/README.md
+- name: Event Datum
+  href: EventDatum/README.md
+- name: Interfaces
+  href: Interfaces/README.md
+- name: Standard Assets
+  href: StandardAssets/README.md
+- name: Utilities
+  href: Utilities/README.md
+  items:
+  - name: Build And Deploy
+    href: Utilities/BuildAndDeploy/README.md
+  - name: Async
+    href: Utilities/Async/ReadMe.md
+  - name: Async License
+    href: Utilities/Async/License.md

BreakingChanges.md

@@ -0,0 +1,2 @@
+# Breaking Changes
+