Remove old guidelines page and update links

api/extension-capabilities/overview.md

@@ -112,7 +112,7 @@ On the other hand, VS Code also offers a set of [Debug Extension API](/api/refer
 
 ## Extension Guidelines
 
-To help make your extension fit seemlessly into the VS Code user interface, refer to the [Extension Guidelines](/api/references/extension-guidelines), where you'll learn the best practices for creating extension UI and conventions for following the preferred VS Code workflows.
+To help make your extension fit seemlessly into the VS Code user interface, refer to the [Extension Guidelines](/api/ux-guidelines/overview), where you'll learn the best practices for creating extension UI and conventions for following the preferred VS Code workflows.
 
 ## Restrictions
 

api/extension-guides/overview.md

@@ -23,7 +23,7 @@ In each guide or sample, you can expect to find:
 
 ## Guides & Samples
 
-Here are the guides on the VS Code website, including their usage of the [VS Code API](/api/references/vscode-api) and [Contribution Points](/api/references/contribution-points). Don't forget to refer to the [Extension Guidelines](/api/references/extension-guidelines) to learn the best practices for creating extensions.
+Here are the guides on the VS Code website, including their usage of the [VS Code API](/api/references/vscode-api) and [Contribution Points](/api/references/contribution-points). Don't forget to refer to the [Extension Guidelines](/api/ux-guidelines/overview) to learn the best practices for creating extensions.
 
 | Guide on VS Code Website | API & Contribution |
 | --- | --- |

api/get-started/wrapping-up.md

@@ -21,7 +21,7 @@ We have a great collection of sample extensions that you can adapt from, and som
 
 ## Extension Guidelines
 
-To help make your extension fit seemlessly into the VS Code user interface, refer to the [Extension Guidelines](/api/references/extension-guidelines), where you'll learn the best practices for creating extension UI and conventions for following the preferred VS Code workflows.
+To help make your extension fit seemlessly into the VS Code user interface, refer to the [Extension Guidelines](/api/ux-guidelines/overview), where you'll learn the best practices for creating extension UI and conventions for following the preferred VS Code workflows.
 
 ## Testing and Publishing
 

api/get-started/your-first-extension.md

@@ -78,7 +78,7 @@ You can learn more about debugging Node.js apps in VS Code in the [Node.js Debug
 
 In the next topic, [Extension Anatomy](/api/get-started/extension-anatomy), we'll take a closer look at the source code of the `Hello World` sample and explain key concepts.
 
-You can find the source code of this tutorial at: [https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample](https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample). The [Extension Guides](/api/extension-guides/overview) topic contains other samples, each illustrating a different VS Code API or Contribution Point, and following the recommendations in our [Extension Guidelines](/api/references/extension-guidelines).
+You can find the source code of this tutorial at: [https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample](https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample). The [Extension Guides](/api/extension-guides/overview) topic contains other samples, each illustrating a different VS Code API or Contribution Point, and following the recommendations in our [Extension Guidelines](/api/ux-guidelines/overview).
 
 ### Using JavaScript
 
@@ -86,4 +86,4 @@ In this guide, we mainly describe how to develop VS Code extension with TypeScri
 
 ### Extension Guidelines
 
-This is also a good time to review our [Extension Guidelines](/api/references/extension-guidelines) so you can start designing your extension to follow the VS Code best practices.
+This is also a good time to review our [Extension Guidelines](/api/ux-guidelines/overview) so you can start designing your extension to follow the VS Code best practices.

api/index.md

@@ -16,7 +16,7 @@ This documentation describes:
 * How to build, run, debug, test, and publish an extension
 * How to take advantage of VS Code's rich Extension API
 * Where to find [guides](https://code.visualstudio.com/api/extension-guides/overview) and [code samples](https://github.com/microsoft/vscode-extension-samples) to help get you started
-* Following our [extension guidelines](/api/references/extension-guidelines) for best practices
+* Following our [extension guidelines](/api/ux-guidelines/overview) for best practices
 
 Code samples are available at [Microsoft/vscode-extension-samples](https://github.com/microsoft/vscode-extension-samples).
 

blogs/2021/10/11/webview-ui-toolkit.md

@@ -17,7 +17,7 @@ We're so excited to announce the public preview of the [Webview UI Toolkit for V
 
 ## What is the Webview UI Toolkit?
 
-At its core, the toolkit is a library of components that developers can use to build user interfaces inside extension webviews. Note that this doesn't change our recommendation to [avoid the use of webviews](https://code.visualstudio.com/api/references/extension-guidelines#webviews) in extensions unless you absolutely need them.
+At its core, the toolkit is a library of components that developers can use to build user interfaces inside extension webviews. Note that this doesn't change our recommendation to [avoid the use of webviews](https://code.visualstudio.com/api/ux-guidelines/webviews) in extensions unless you absolutely need them.
 
 Features of the library include:
 

release-notes/v1_53.md

@@ -331,7 +331,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
 
 ### Extension guidelines
 
-There is now a set of detailed [extension guidelines](https://code.visualstudio.com/api/references/extension-guidelines) for extension authors. The guidelines cover best practices for contributing to VS Code's users interface and conventions for notifications and status updates.
+There is now a set of detailed [extension guidelines](https://code.visualstudio.com/api/ux-guidelines/overview) for extension authors. The guidelines cover best practices for contributing to VS Code's users interface and conventions for notifications and status updates.
 
 As an example, below are the Do's and Dont's for contributing commands to the Command Palette: