Fix metadata, TOC, and include folder

Author: ghogen

connected-environment/docfx.json

@@ -41,7 +41,8 @@
       "breadcrumb_path": "/visualstudio/connected-environment/breadcrumb/toc.json",
       "extendBreadcrumb": true,
       "ms.service": "connected-environment",
-      "ROBOTS":  "NOINDEX,NOFOLLOW"
+      "ROBOTS":  "NOINDEX,NOFOLLOW",
+      "titleSuffix": "Visual Studio Connected Environment"
     },
     "fileMetadata": {},
     "template": [],

connected-environment/get-started-netcore-01.md

@@ -11,11 +11,11 @@ manager: "ghogen"
 ---
 # Get Started on Connected Environment with .NET Core
 
-[!INCLUDE[](common/learning-objectives.md)]
+[!INCLUDE[](includes/learning-objectives.md)]
 
-[!INCLUDE[](common/see-troubleshooting.md)]
+[!INCLUDE[](includes/see-troubleshooting.md)]
 
-[!INCLUDE[](common/install-cli-and-vscode.md)]
+[!INCLUDE[](includes/install-cli-and-vscode.md)]
 
 We're now ready to create a Kubernetes-based development environment in Azure.
 

connected-environment/get-started-netcore-02.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Install tools](get-started-netcore-01.md)
 
-[!INCLUDE[](common/sign-into-azure.md)]
+[!INCLUDE[](includes/sign-into-azure.md)]
 
-[!INCLUDE[](common/create-env-cli.md)]
+[!INCLUDE[](includes/create-env-cli.md)]
 
 While we're waiting for the environment to be create, let's start developing code.
 

connected-environment/get-started-netcore-03.md

@@ -21,11 +21,11 @@ dotnet new mvc --name webfrontend
 
 Alternatively, **download sample code from GitHub** by navigating to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce/samples/dotnetcore/getting-started/webfrontend`.
 
-[!INCLUDE[](common/vsce-init.md)]
+[!INCLUDE[](includes/vsce-init.md)]
 
-[!INCLUDE[](common/ensure-env-created.md)]
+[!INCLUDE[](includes/ensure-env-created.md)]
 
-[!INCLUDE[](common/build-and-run-in-k8s-cli.md)]
+[!INCLUDE[](includes/build-and-run-in-k8s-cli.md)]
 
 ## Update a content file
 Connected Environment isn't just about getting code running in Kubernetes - it's about enabling you to quickly and iteratively see your code changes take effect in a Kubernetes environment in the cloud.

connected-environment/get-started-netcore-04.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Create an ASP.NET Core Web App](get-started-netcore-03.md)
 
-[!INCLUDE[](common/debug-intro.md)]
+[!INCLUDE[](includes/debug-intro.md)]
 
-[!INCLUDE[](common/init-debug-assets-vscode.md)]
+[!INCLUDE[](includes/init-debug-assets-vscode.md)]
 
 
 ## Select the VSCE debug configuration
@@ -33,7 +33,7 @@ Hit **F5** to debug your code in Kubernetes.
 
 As with the `up` command, code is synced to the development environment, and a container is built and deployed to Kubernetes. This time, of course, the debugger is attached to the remote container.
 
-[!INCLUDE[](common/tip-vscode-status-bar-url.md)]
+[!INCLUDE[](includes/tip-vscode-status-bar-url.md)]
 
 Set a breakpoint in a server-side code file, for example within the `Index()` function in the `Controllers/HomeController.cs` source file. Refreshing the browser page causes the breakpoint to hit.
 

connected-environment/get-started-netcore-06.md

@@ -13,7 +13,7 @@ manager: "ghogen"
 
 Previous step: [Call another container](get-started-netcore-05.md)
 
-[!INCLUDE[](common/team-development-1.md)]
+[!INCLUDE[](includes/team-development-1.md)]
 
 Let's see it in action:
 1. Go to the VS Code window for `mywebapi` and make a code edit to the `string Get(int id)` method, for example:
@@ -26,7 +26,7 @@ public string Get(int id)
 }
 ```
 
-[!INCLUDE[](common/team-development-2.md)]
+[!INCLUDE[](includes/team-development-2.md)]
 
 > [!div class="nextstepaction"]
 > [Next](get-started-netcore-07.md)

connected-environment/get-started-netcore-07.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Learn about team development](get-started-netcore-06.md)
 
-[!INCLUDE[](common/well-done.md)]
+[!INCLUDE[](includes/well-done.md)]
 
-[!INCLUDE[](common/take-survey.md)]
+[!INCLUDE[](includes/take-survey.md)]
 
-[!INCLUDE[](common/clean-up.md)]
+[!INCLUDE[](includes/clean-up.md)]
 

connected-environment/get-started-netcore-visualstudio-01.md

@@ -18,7 +18,7 @@ In this guide, you will learn how to:
 1. Independently develop two separate services, and used Kubernetes' DNS service discovery to make a call to another service.
 1. Productively develop and test your code in a team environment.
 
-[!INCLUDE[](common/see-troubleshooting.md)]
+[!INCLUDE[](includes/see-troubleshooting.md)]
 
 ## Install the Connected Environment CLI
 Connected Environment requires minimal local machine setup. Most of your development environment's configuration gets stored in the cloud, and is shareable with other users.

connected-environment/get-started-netcore-visualstudio-07.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Learn about team development](get-started-netcore-visualstudio-06.md)
 
-[!INCLUDE[](common/well-done.md)]
+[!INCLUDE[](includes/well-done.md)]
 
-[!INCLUDE[](common/take-survey.md)]
+[!INCLUDE[](includes/take-survey.md)]
 
-[!INCLUDE[](common/clean-up.md)]
+[!INCLUDE[](includes/clean-up.md)]
 

connected-environment/get-started-nodejs-01.md

@@ -11,11 +11,11 @@ manager: "ghogen"
 ---
 # Get Started on Connected Environment with Node.js
 
-[!INCLUDE[](common/learning-objectives.md)]
+[!INCLUDE[](includes/learning-objectives.md)]
 
-[!INCLUDE[](common/see-troubleshooting.md)]
+[!INCLUDE[](includes/see-troubleshooting.md)]
 
-[!INCLUDE[](common/install-cli-and-vscode.md)]
+[!INCLUDE[](includes/install-cli-and-vscode.md)]
 
 
 We're now ready to create a Kubernetes-based development environment in Azure.

connected-environment/get-started-nodejs-02.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Install tools](get-started-nodejs-01.md)
 
-[!INCLUDE[](common/sign-into-azure.md)]
+[!INCLUDE[](includes/sign-into-azure.md)]
 
-[!INCLUDE[](common/create-env-cli.md)]
+[!INCLUDE[](includes/create-env-cli.md)]
 
 While we're waiting for the environment to be create, let's start developing code!
 

connected-environment/get-started-nodejs-03.md

@@ -16,11 +16,11 @@ Previous step: [Create a Kubernetes development environment in Azure](get-starte
 ## Create a Node.js Web App
 Download code from GitHub by navigating to https://github.com/Azure/vsce and select **Clone or Download** to download the GitHub repository to your local environment. The code for this guide is in `vsce/samples/nodejs/getting-started/webfrontend`.
 
-[!INCLUDE[](common/vsce-init.md)]
+[!INCLUDE[](includes/vsce-init.md)]
 
-[!INCLUDE[](common/ensure-env-created.md)]
+[!INCLUDE[](includes/ensure-env-created.md)]
 
-[!INCLUDE[](common/build-and-run-in-k8s-cli.md)]
+[!INCLUDE[](includes/build-and-run-in-k8s-cli.md)]
 
 ## Update a content file
 Connected Environment isn't just about getting code running in Kubernetes - it's about enabling you to quickly and iteratively see your code changes take effect in a Kubernetes environment in the cloud.

connected-environment/get-started-nodejs-04.md

@@ -13,9 +13,9 @@ manager: "ghogen"
 
 Previous step: [Create a Node.js container in Kubernetes](get-started-nodejs-03.md)
 
-[!INCLUDE[](common/debug-intro.md)]
+[!INCLUDE[](includes/debug-intro.md)]
 
-[!INCLUDE[](common/init-debug-assets-vscode.md)]
+[!INCLUDE[](includes/init-debug-assets-vscode.md)]
 
 
 ## Select the VSCE debug configuration
@@ -32,7 +32,7 @@ Hit **F5** to debug your code in Kubernetes!
 
 Similar to the `up` command, code is synced to the development environment when you start debugging, and a container is built and deployed to Kubernetes. This time, of course, the debugger is attached to the remote container.
 
-[!INCLUDE[](common/tip-vscode-status-bar-url.md)]
+[!INCLUDE[](includes/tip-vscode-status-bar-url.md)]
 
 Set a breakpoint in a server-side code file, for example within the `app.get('/api'...` in  `server.js`. Refresh the browser page, or press the 'Say It Again' button, and you should hit the breakpoint and be able to step through code.
 

connected-environment/get-started-nodejs-06.md

@@ -13,7 +13,7 @@ manager: "ghogen"
 
 Previous step: [Call a service running in a separate container](get-started-nodejs-05.md)
 
-[!INCLUDE[](common/team-development-1.md)]
+[!INCLUDE[](includes/team-development-1.md)]
 
 Let's see it in action:
 1. Go to the VS Code window for `mywebapi` and make a code edit to the default GET `/` handler, for example:
@@ -24,7 +24,7 @@ app.get('/', function (req, res) {
 });
 ```
 
-[!INCLUDE[](common/team-development-2.md)]
+[!INCLUDE[](includes/team-development-2.md)]
 
 > [!div class="nextstepaction"]
 > [Next](get-started-nodejs-07.md)

connected-environment/get-started-nodejs-07.md

@@ -13,8 +13,8 @@ manager: "ghogen"
 
 Previous step: [Learn about team development](get-started-nodejs-06.md)
 
-[!INCLUDE[](common/well-done.md)]
+[!INCLUDE[](includes/well-done.md)]
 
-[!INCLUDE[](common/take-survey.md)]
+[!INCLUDE[](includes/take-survey.md)]
 
-[!INCLUDE[](common/clean-up.md)]
+[!INCLUDE[](includes/clean-up.md)]

connected-environment/how-to/share-dev-environment.md

@@ -1,3 +1,14 @@
+---
+title: "How to share a development environment | Microsoft Docs"
+author: "johnsta"
+ms.author: "johnsta"
+ms.date: "3/12/2018"
+ms.topic: "article"
+ms.technology: "vsce-kubernetes"
+description: "Rapid Kubernetes development with containers and microservices on Azure"
+keywords: "Docker, Kubernetes, Azure, AKS, Azure Container Service, containers"
+manager: "ghogen"
+---
 # Share a Development Environment
 
 With Connected Environment, you can share your development environment with others on your team. Each developer can work in their own space without fear of breaking others. Also, working together in one environment can enable you to test code end-to-end without having to create mocks or simulate dependencies. See the [Learn about team development](../get-started-nodejs-06.md) guide for more information.

connected-environment/how-to/use-kubectl-with-vsce.md

@@ -1,3 +1,14 @@
+---
+title: "How to use kubectl with a Connected Environment | Microsoft Docs"
+author: "johnsta"
+ms.author: "johnsta"
+ms.date: "03/12/2018"
+ms.topic: "article"
+ms.technology: "vsce-kubernetes"
+description: "Rapid Kubernetes development with containers and microservices on Azure"
+keywords: "Docker, Kubernetes, Azure, AKS, Azure Container Service, containers"
+manager: "ghogen"
+---
 # Use `kubectl` with a Connected Environment
 
 You can access the Kubernetes cluster within a Connected Environment, and use existing Kubernetes tools like `kubectl`.