Refactor Tools node content

Author: Greg Van Liew

blogs/2017/03/07/extension-pack-roundup.md

@@ -19,7 +19,7 @@ Creating a theme for this blog is a natural fit for a relatively new part of the
 
 ## How do I make an Extension Pack? 
 
-It is very easy to make your own Extension Pack. Follow the instructions on installing the Yeoman VS Code [extension generator](https://code.visualstudio.com/docs/tools/yocode). 
+It is very easy to make your own Extension Pack. Follow the instructions on installing the Yeoman VS Code [extension generator](https://code.visualstudio.com/docs/extensions/yocode). 
 
 Once the Yeoman generator is installed, run the following command:
 

docs/editor/extension-gallery.md

@@ -131,8 +131,8 @@ VS Code prompts a user to install the recommended extensions when a workspace is
 
 Here are a few topics you may find interesting...
 
-* [Publishing to the Marketplace](/docs/tools/vscecli.md) - Publish your own customization or extension to the VS Code Marketplace
-* [Yo Code](/docs/tools/yocode.md) - Learn how the Yo Code extension generator can scaffold out new extensions and package existing TextMate files.
+* [Publishing to the Marketplace](/docs/extensions/publish-extension.md) - Publish your own customization or extension to the VS Code Marketplace
+* [Extension Generator](/docs/extensions/yocode.md) - Learn how the Yo Code extension generator can scaffold out new extensions and package existing TextMate files.
 * [Extending Visual Studio Code](/docs/extensions/overview.md) - Start learning about VS Code extensibility
 * [Your First Extension](/docs/extensions/example-hello-world.md) - Try creating a simple Hello World extension
 
@@ -158,7 +158,7 @@ Once you've downloaded an extension, you can side load it by renaming the `.zip`
 
 **Q: Can VS Code read TextMate bundles directly?**
 
-**A**: No, VS Code can read some TextMate files such as .tmTheme and .tmLanguage but can not install full TextMate bundles. Also in order to use TextMate theme and syntax files, VS Code needs extra metadata for integration. The [Yo Code](/docs/tools/yocode.md) extension generator makes it easy to package these files for use in VS Code. See the [Themes, Snippets, and Colorizers](/docs/extensions/themes-snippets-colorizers.md) topic in the Extension Authoring section for details.
+**A**: No, VS Code can read some TextMate files such as .tmTheme and .tmLanguage but can not install full TextMate bundles. Also in order to use TextMate theme and syntax files, VS Code needs extra metadata for integration. The [Yo Code](/docs/extensions/yocode.md) extension generator makes it easy to package these files for use in VS Code. See the [Themes, Snippets, and Colorizers](/docs/extensions/themes-snippets-colorizers.md) topic in the Extension Authoring section for details.
 
 **Q: Can I install Visual Studio Community extensions (shipped in .vsix) in Visual Studio Code?**
 

docs/extensionAPI/extension-manifest.md

@@ -17,7 +17,7 @@ Name | Required | Type | Details
 ---- |:--------:| ---- | -------
 `name` | Y | `string` | The name of the extension - should be all lowercase with no spaces.
 `version` | Y | `string` | [SemVer](http://semver.org/) compatible version.
-`publisher` | Y | `string` | The [publisher name](/docs/tools/vscecli.md#publishers-and-personal-access-tokens)
+`publisher` | Y | `string` | The [publisher name](/docs/extensions/publish-extension.md#publishers-and-personal-access-tokens)
 `engines` | Y | `object` | An object containing at least the `vscode` key matching the versions of VS Code that the extension is compatible with.  Cannot be `*`. For example: `^0.10.5` indicates compatibility with a minimum VS Code version of `0.10.5`.
 `license` | | `string` | Refer to [npm's documentation](https://docs.npmjs.com/files/package.json#license). If you do have a `LICENSE` file in the root of your extension, the value for `license` should be `"SEE LICENSE IN <filename>"`.
 `displayName` | | `string`| The display name for the extension used in the Marketplace.
@@ -34,7 +34,7 @@ Name | Required | Type | Details
 `dependencies` | | `object` | Any runtime Node.js dependencies your extensions needs. Exactly the same as [npm's `dependencies`](https://docs.npmjs.com/files/package.json#dependencies).
 `devDependencies` | | `object` | Any development Node.js dependencies your extension needs. Exactly the same as [npm's `devDependencies`](https://docs.npmjs.com/files/package.json#devdependencies).
 `extensionDependencies` | | `array` | An array with the ids of extensions that this extension depends on. These other extensions will be installed when the primary extension is installed. The id of an extension is always `${publisher}.${name}`. For example: `vscode.csharp`.
-`scripts` | | `object` | Exactly the same as [npm's `scripts`](https://docs.npmjs.com/misc/scripts) but with [extra VS Code specific fields](/docs/tools/vscecli.md#pre-publish-step).
+`scripts` | | `object` | Exactly the same as [npm's `scripts`](https://docs.npmjs.com/misc/scripts) but with [extra VS Code specific fields](/docs/extensions/publish-extension.md#pre-publish-step).
 `icon` | | `string` | The path to a 128x128 pixel icon.
 
 Also check [npm's `package.json` reference](https://docs.npmjs.com/files/package.json).

docs/extensionAPI/extension-points.md

@@ -355,7 +355,7 @@ Contribute a TextMate grammar to a language. You must provide the `language` thi
 }
 ```
 
-See [Adding Language Colorization](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmLanguage files as VS Code extensions.
+See [Adding Language Colorization](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/extensions/yocode.md) to quickly package TextMate .tmLanguage files as VS Code extensions.
 
 ![grammars extension point example](images/extension-points/grammars.png)
 
@@ -377,7 +377,7 @@ Contribute a TextMate theme to VS Code. You must specify a label, whether the th
 
 ![themes extension point example](images/extension-points/themes.png)
 
-See [Changing the Color Theme](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmTheme files as VS Code extensions.
+See [Changing the Color Theme](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/extensions/yocode.md) to quickly package TextMate .tmTheme files as VS Code extensions.
 
 ## contributes.snippets
 

docs/extensionAPI/overview.md

@@ -12,7 +12,7 @@ MetaDescription: Learn the details of Visual Studio Code's rich extensibility (p
 
 This section of our documentation goes into detail on the various features of VS Code extensibility.  It's worth reviewing the introduction on the [extensions](/docs/extensions/overview.md) as well as going through the ['Hello World'](/docs/extensions/example-hello-world.md) example before digging in too deeply here.
 
-The easiest way to see VS Code extensions in action is via the [Extension Marketplace](/docs/editor/extension-gallery.md).  Once you have built your first extension, it can be [published](/docs/tools/vscecli.md) for others to install.
+The easiest way to see VS Code extensions in action is via the [Extension Marketplace](/docs/editor/extension-gallery.md).  Once you have built your first extension, it can be [published](/docs/extensions/publish-extension.md) for others to install.
 
 ## The Extensibility Reference Documents
 

docs/extensionAPI/patterns-and-principles.md

@@ -107,7 +107,7 @@ Your extension can depend on [Node.js](https://nodejs.org) modules at runtime. S
 
 Visual Studio Code **will not** install your extension's dependencies when a user installs it, so you must `npm install` before publishing. The extension's publishing package will contain all of its dependencies within. You can run `vsce ls` to list all the files that `vsce` will include in the package.
 
-You can create a `.vscodeignore` file to exclude some files from being included in your extension's package. See the `vsce` publishing tool topic for [details](https://code.visualstudio.com/docs/tools/vscecli.md#vscodeignore) about using a `.vscodeignore` file.
+You can create a `.vscodeignore` file to exclude some files from being included in your extension's package. See the `vsce` publishing tool topic for [details](https://code.visualstudio.com/docs/extensions/publish-extension.md#vscodeignore) about using a `.vscodeignore` file.
 
 ## Next Steps
 

docs/extensions/debugging-extensions.md

@@ -1,5 +1,5 @@
 ---
-Order: 8
+Order: 9
 Area: extensions
 TOCTitle: Running and Debugging Extensions
 ContentId: 44569A0C-7196-48E6-A5EE-FC5AAAAD32F3
@@ -20,7 +20,7 @@ You can use VS Code to develop an extension for VS Code and VS Code provides sev
 
 ## Creating an Extension
 
-We suggest you start your extension by scaffolding out the basic files. You can use the `yo code` Yeoman generator to do this and we cover the details in the [Yo Code document](/docs/tools/yocode.md).  The generator will ensure everything is set up so you have a great development experience.
+We suggest you start your extension by scaffolding out the basic files. You can use the `yo code` Yeoman generator to do this and we cover the details in the [extension generator](/docs/extensions/yocode.md) topic.  The generator will ensure everything is set up so you have a great development experience.
 
 ## Running and Debugging your Extension
 
@@ -77,7 +77,7 @@ your changes. You have two options to do this:
 ## Next Steps
 
 * [Testing your Extension](/docs/extensions/testing-extensions.md) - Learn how to write unit and integration tests for your extension
-* [Publishing Tool](/docs/tools/vscecli.md) - Publish your extension with the vsce command line tool.
+* [Publishing Tool](/docs/extensions/publish-extension.md) - Publish your extension with the vsce command line tool.
 * [Extension Manifest file](/docs/extensionAPI/extension-manifest.md) - VS Code extension manifest file reference
 * [Extension API](/docs/extensionAPI/overview.md) - Learn about the VS Code extensibility APIs
 

docs/extensions/example-debuggers.md

@@ -1,5 +1,5 @@
 ---
-Order: 5
+Order: 6
 Area: extensions
 TOCTitle: Example-Debuggers
 ContentId: 49EF49AD-8BE6-4D46-ADC8-D678BDC04E85
@@ -314,4 +314,4 @@ The variable can now be used in any string typed value of a launch configuration
 Once you have created your debug adapter you can publish it to the Marketplace:
 
 * update the attributes in the `package.json` to reflect the naming and purpose of your debug adapter.
-* upload to the Marketplace as described in [Share an Extension](/docs/tools/vscecli.md) section.
+* upload to the Marketplace as described in [Share an Extension](/docs/extensions/publish-extension.md) section.

docs/extensions/example-hello-world.md

@@ -1,5 +1,5 @@
 ---
-Order: 2
+Order: 3
 Area: extensions
 TOCTitle: Example-Hello World
 ContentId: DC915D6C-13D4-4022-9101-57C4A4118B07
@@ -23,7 +23,7 @@ You need [Node.js](https://nodejs.org/en/) installed and available in your `$PAT
 
 The simplest way to add your own functionality to VS Code is through adding a command. A command registers a callback function which can be invoked from the **Command Palette** or with a key binding.
 
-We have written a Yeoman generator to help get you started. Install Yeoman and the [Yeoman VS Code Extension generator](/docs/tools/yocode.md) and scaffold a new extension:
+We have written a Yeoman generator to help get you started. Install Yeoman and the [Yeoman VS Code Extension generator](/docs/extensions/yocode.md) and scaffold a new extension:
 
 ```sh
 npm install -g yo generator-code
@@ -181,7 +181,7 @@ export function activate(context: vscode.ExtensionContext) {
 * `.vscode/launch.json` defines launching VS Code in the Extension Development mode. It also points with `preLaunchTask` to a task defined in `.vscode/tasks.json` that runs the TypeScript compiler.
 * `.vscode/settings.json` by default excludes the `out` folder.  You can modify which file types you want to hide.
 * `.gitignore` - Tells Git version control which patterns to ignore.
-* [`.vscodeignore`](/docs/tools/vscecli.md#advanced-usage) - Tells the packaging tool which files to ignore when publishing the extension.
+* [`.vscodeignore`](/docs/extensions/publish-extension.md#advanced-usage) - Tells the packaging tool which files to ignore when publishing the extension.
 * `README.md` - README file describing your extension for VS Code users.
 * `vsc-extension-quickstart.md` - A Quick Start guide for you.
 * `test/extension.test.ts` - you can put your extension unit tests in here and run your tests against the VS Code API (see [Testing Your Extension](/docs/extensions/testing-extensions.md))
@@ -246,7 +246,7 @@ So far, the extension you have written only runs in a special instance of VS Cod
 
 ## Publishing your Extension
 
-Read about how to [Share an Extension](/docs/tools/vscecli.md).
+Read about how to [Share an Extension](/docs/extensions/publish-extension.md).
 
 ## Next Steps
 

docs/extensions/example-language-server.md

@@ -1,5 +1,5 @@
 ---
-Order: 4
+Order: 5
 Area: extensions
 TOCTitle: Example-Language Server
 ContentId: A8CBE8D6-1FEE-47BF-B81E-D79FA0DB5D03

docs/extensions/example-word-count.md

@@ -1,5 +1,5 @@
 ---
-Order: 3
+Order: 4
 Area: extensions
 TOCTitle: Example-Word Count
 ContentId: 4D9132DC-CDDB-4E07-B2DD-9A7E168BE384
@@ -277,13 +277,13 @@ So far, the extension you have written only runs in a special instance of VS Cod
 
 ## Publishing your Extension
 
-Read about how to [Share an Extension](/docs/tools/vscecli.md).
+Read about how to [Share an Extension](/docs/extensions/publish-extension.md).
 
 ## Next Steps
 
 Read on to find out about:
 
-* [Yo Code](/docs/tools/yocode.md) - learn about other options in Yo Code
-* [Extension API](/docs/extensionAPI/overview.md) - Get an overview of the Extension API
-* [Publishing Tool](/docs/tools/vscecli.md) - Learn how to publish an extension to the public Marketplace
-* [Editor API](/docs/extensionAPI/vscode-api.md#window) - Learn more about Text Documents, Text Editors and editing text
+* [Extension Generator](/docs/extensions/yocode.md) - Learn about other options in the Yo Code extension generator.
+* [Extension API](/docs/extensionAPI/overview.md) - Get an overview of the Extension API.
+* [Publishing Tool](/docs/extensions/publish-extension.md) - Learn how to publish an extension to the public Marketplace.
+* [Editor API](/docs/extensionAPI/vscode-api.md#window) - Learn more about Text Documents, Text Editors and editing text.

docs/tools/images/vscecli/publishers1.png renamed to docs/extensions/images/publish-extension/publishers1.png

@@ -1,5 +1,5 @@
 ---
-Order: 10
+Order: 11
 Area: extensions
 TOCTitle: Installing Extensions
 ContentId: 8D19F206-8CB3-498D-BDD1-317B4104EDD0
@@ -44,10 +44,9 @@ You can also install a `.vsix` with the **Install from VSIX...** command in the
 
 ### Sharing Privately with Others
 
-If you want to share your extension or customization with others privately, you can simply send them a copy of the output from the generator and ask them to add it under their `.vscode/extensions` folder. Alternatively, package your extension using the [vsce publishing tool](/docs/tools/vscecli.md) by running `vsce package` and send them the `.vsix` file.
+If you want to share your extension or customization with others privately, you can simply send them a copy of the output from the generator and ask them to add it under their `.vscode/extensions` folder. Alternatively, package your extension using the [vsce publishing tool](/docs/extensions/publish-extension.md) by running `vsce package` and send them the `.vsix` file.
 
 ## Next Steps
 
 * [Extension Marketplace](/docs/editor/extension-gallery.md) - Learn more about VS Code's public extension Marketplace.
-* [Publishing Extensions](/docs/extensions/publish-extension.md) - Put your extension on the Marketplace.
-* [Publishing Tool Reference](/docs/tools/vscecli.md) - Learn how to package and publish your extensions.
+* [Publishing Extensions](/docs/extensions/publish-extension.md) - Put your extension on the Marketplace.

docs/tools/images/vscecli/publishers2.png renamed to docs/extensions/images/publish-extension/publishers2.png

@@ -78,4 +78,4 @@ We also have great support for [writing and running tests](/docs/extensions/test
 
 * [Your First Extension](/docs/extensions/example-hello-world.md) - Try creating a simple Hello World extension
 * [Extension API](/docs/extensionAPI/overview.md) - Learn about the VS Code extensibility APIs
-* [Samples](/docs/tools/samples.md) - A list of extension samples you can review and build
+* [Samples](/docs/extensions/samples.md) - A list of extension samples you can review and build