Move some articles out of the Design section (#4989)

Author: jwmsft

.openpublishing.redirection.json

@@ -1487,13 +1487,13 @@
     },
     {
       "source_path": "uwp/controls-and-patterns/xaml-styles.md",
-      "redirect_url": "/windows/uwp/design/controls-and-patterns/xaml-styles",
-      "redirect_document_id": true
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-styles",
+      "redirect_document_id": false
     },
     {
       "source_path": "uwp/controls-and-patterns/xaml-theme-resources.md",
-      "redirect_url": "/windows/uwp/design/controls-and-patterns/xaml-theme-resources",
-      "redirect_document_id": true
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-theme-resources",
+      "redirect_document_id": false
     },
     {
       "source_path": "uwp/controls-and-patterns/tiles-and-notifications/channel-types.md",
@@ -1822,7 +1822,7 @@
     },
     {
       "source_path": "uwp/layout/show-multiple-views.md",
-      "redirect_url": "/windows/uwp/design/layout/show-multiple-views",
+      "redirect_url": "/windows/uwp/ui-input/show-multiple-views",
       "redirect_document_id": true
     },
     {
@@ -2027,7 +2027,7 @@
     },
     {
       "source_path": "uwp/graphics/3-d-perspective-effects.md",
-      "redirect_url": "/windows/uwp/design/layout/3-d-perspective-effects",
+      "redirect_url": "/windows/apps/develop/platform/xaml/3-d-perspective-effects",
       "redirect_document_id": false
     },
     {
@@ -6252,12 +6252,12 @@
     },
     {
       "source_path": "uwp/design/controls-and-patterns/xaml-styles.md",
-      "redirect_url": "/windows/apps/design/style/xaml-styles",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-styles",
       "redirect_document_id": false
     },
     {
       "source_path": "uwp/design/controls-and-patterns/xaml-theme-resources.md",
-      "redirect_url": "/windows/apps/design/style/xaml-theme-resources",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-theme-resources",
       "redirect_document_id": false
     },
     {
@@ -6637,7 +6637,7 @@
     },
     {
       "source_path": "uwp/design/layout/3-d-perspective-effects.md",
-      "redirect_url": "/windows/apps/design/layout/3-d-perspective-effects",
+      "redirect_url": "/windows/apps/develop/platform/xaml/3-d-perspective-effects",
       "redirect_document_id": false
     },
     {
@@ -6647,12 +6647,12 @@
     },
     {
       "source_path": "uwp/design/layout/app-window.md",
-      "redirect_url": "/windows/apps/design/layout/app-window",
+      "redirect_url": "/windows/uwp/ui-input/app-window",
       "redirect_document_id": false
     },
     {
       "source_path": "uwp/design/layout/application-view.md",
-      "redirect_url": "/windows/apps/design/layout/application-view",
+      "redirect_url": "/windows/uwp/ui-input/application-view",
       "redirect_document_id": false
     },
     {
@@ -6712,12 +6712,12 @@
     },
     {
       "source_path": "uwp/design/layout/show-multiple-views.md",
-      "redirect_url": "/windows/apps/design/layout/show-multiple-views",
+      "redirect_url": "/windows/uwp/ui-input/show-multiple-views",
       "redirect_document_id": false
     },
     {
       "source_path": "uwp/design/layout/transforms.md",
-      "redirect_url": "/windows/apps/design/layout/transforms",
+      "redirect_url": "/windows/apps/develop/platform/xaml/transforms",
       "redirect_document_id": false
     },
     {
@@ -7097,7 +7097,7 @@
     },
     {
       "source_path": "uwp/design/style/brushes.md",
-      "redirect_url": "/windows/apps/design/style/brushes",
+      "redirect_url": "/windows/apps/develop/platform/xaml/brushes",
       "redirect_document_id": false
     },
     {
@@ -7117,7 +7117,7 @@
     },
     {
       "source_path": "uwp/design/style/reveal-focus.md",
-      "redirect_url": "/windows/apps/design/style/reveal-focus",
+      "redirect_url": "/windows/uwp/ui-input/reveal-focus",
       "redirect_document_id": false
     },
     {
@@ -8574,6 +8574,61 @@
       "source_path": "hub/dev-home/quickstart-playground.md",
       "redirect_url": "/windows/dev-home/#experimental-features",
       "redirect_document_id": false
+    },   
+    {
+      "source_path": "hub/apps/design/style/xaml-control-templates.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-control-templates",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/style/xaml-resource-dictionary.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-resource-dictionary",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/style/xaml-styles.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-styles",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/style/xaml-theme-resources.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/xaml-theme-resources",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/layout/transforms.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/transforms",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/layout/3-d-perspective-effects.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/3-d-perspective-effects",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/style/brushes.md",
+      "redirect_url": "/windows/apps/develop/platform/xaml/brushes",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/style/reveal-focus.md",
+      "redirect_url": "/windows/uwp/ui-input/reveal-focus",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/layout/app-window.md",
+      "redirect_url": "/windows/uwp/ui-input/app-window",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/layout/application-view.md",
+      "redirect_url": "/windows/uwp/ui-input/application-view",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/layout/show-multiple-views.md",
+      "redirect_url": "/windows/uwp/ui-input/show-multiple-views",
+      "redirect_document_id": false
     },
     {
       "source_path": "hub/android/defender-settings.md",

hub/apps/design/accessibility/developing-inclusive-windows-apps.md

@@ -50,7 +50,7 @@ XAML
 ```xaml
 <Button Background="{ThemeResource ButtonBackgroundThemeBrush}">OK</Button>
 ```
-For more information about using system colors and resources, see [XAML theme resources](../style/xaml-theme-resources.md).
+For more information about using system colors and resources, see [XAML theme resources](../../develop/platform/xaml/xaml-theme-resources.md).
 
 As long as you haven’t overridden system colors, a UWP app supports high-contrast themes by default. If a user has chosen that they want the system to use a high-contrast theme from system settings or accessibility tools, the framework automatically uses colors and style settings that produce a high-contrast layout and rendering for controls and components in the UI.   
 

hub/apps/design/basics/titlebar-design.md

@@ -55,7 +55,7 @@ This section describes the design recommendations and behaviors of the parts of
 - Place the window title 16px from the window icon or back button.
   - If neither an icon nor back button are present, place the window title 16px from the left-most border in LTR, or right-most border in RTL.
 - The window title should use the Segoe UI Variable (if available) or Segoe UI font.
-- The window title should use _caption_ style text (see [XAML type ramp](../style/xaml-theme-resources.md#the-xaml-type-ramp)).
+- The window title should use _caption_ style text (see [XAML type ramp](../../develop/platform/xaml/xaml-theme-resources.md#the-xaml-type-ramp)).
 - The window title can be truncated, and an ellipsis added if the window width is smaller than the length of the title bar elements. The icon and caption buttons (min, max and close) should always be fully visible.
 
 **Behavior**

hub/apps/design/controls/breadcrumbbar.md

@@ -149,7 +149,7 @@ private void BreadcrumbBar1_ItemClicked(muxc.BreadcrumbBar sender, muxc.Breadcru
 
 ### Lightweight styling
 
-You can modify the default Style and ControlTemplate to give the control a unique appearance. See the Control Style and Template section of the BreadcrumbBar API docs for a list of the available theme resources. For more info, see the [Light-weight styling section](../style/xaml-styles.md#lightweight-styling) of the [Styling controls](../style/xaml-styles.md) article.
+You can modify the default Style and ControlTemplate to give the control a unique appearance. See the Control Style and Template section of the BreadcrumbBar API docs for a list of the available theme resources. For more info, see the [Light-weight styling section](../../develop/platform/xaml/xaml-styles.md#lightweight-styling) of the [Styling controls](../../develop/platform/xaml/xaml-styles.md) article.
 
 ## Code examples
 

hub/apps/design/controls/command-bar-flyout.md

@@ -196,7 +196,7 @@ Here, an AppBarElementContainer is used to add extra elements to a command bar f
 > [!TIP]
 > By default, elements designed for the app canvas might not look right in a command bar. When you add an element using AppBarElementContainer, there are some steps you should take to make the element match other command bar elements:
 >
-> - Override the default brushes with [lightweight styling](../style/xaml-styles.md#lightweight-styling) to make the element's background and border match the app bar buttons.
+> - Override the default brushes with [lightweight styling](../../develop/platform/xaml/xaml-styles.md#lightweight-styling) to make the element's background and border match the app bar buttons.
 > - Adjust the size and position of the element.
 > - Wrap icons in a Viewbox with a Width and Height of 16px.
 

hub/apps/design/controls/controls-and-events-intro.md

@@ -20,7 +20,7 @@ In Windows app development, a *control* is a UI element that displays content or
 
 A *pattern* is a recipe for modifying a control or combining several controls to make something new. For example, the [list/details](list-details.md) pattern is a way that you can use a [SplitView](split-view.md) control for app navigation. Similarly, you can customize the template of a [NavigationView](navigationview.md) control to implement the tab pattern.
 
-In many cases, you can use a control as-is. But XAML controls separate function from structure and appearance, so you can make various levels of modification to make them fit your needs. In the [Style](../style/index.md) section, you can learn how to use [XAML styles](../style/xaml-styles.md) and [control templates](../style/xaml-control-templates.md) to modify a control.
+In many cases, you can use a control as-is. But XAML controls separate function from structure and appearance, so you can make various levels of modification to make them fit your needs. In the [Style](../style/index.md) section, you can learn how to use [XAML styles](../../develop/platform/xaml/xaml-styles.md) and [control templates](../../develop/platform/xaml/xaml-control-templates.md) to modify a control.
 
 In this section, we provide guidance for each of the XAML controls you can use to build your app UI. To start, this article shows you how to add controls to your app. There are 3 key steps to using controls to your app:
 

hub/apps/design/controls/custom-transport-controls.md

@@ -51,7 +51,7 @@ The [**ControlTemplate**](/uwp/api/Windows.UI.Xaml.Controls.ControlTemplate) is
 - The third section contains the [**Grid**](/uwp/api/Windows.UI.Xaml.Controls.Grid) that holds that various MediaTransportControls elements together and defines how the components are laid out.
 
 > [!NOTE]
-> For more info about modifying templates, see [Control templates](../style/xaml-control-templates.md). You can use a text editor or similar editors in your IDE to open the XAML files in \(*Program Files*)\Windows Kits\10\DesignTime\CommonConfiguration\Neutral\UAP\\(*SDK version*)\Generic. The default style and template for each control is defined in the **generic.xaml** file. You can find the MediaTransportControls template in generic.xaml by searching for "MediaTransportControls".
+> For more info about modifying templates, see [Control templates](../../develop/platform/xaml/xaml-control-templates.md). You can use a text editor or similar editors in your IDE to open the XAML files in \(*Program Files*)\Windows Kits\10\DesignTime\CommonConfiguration\Neutral\UAP\\(*SDK version*)\Generic. The default style and template for each control is defined in the **generic.xaml** file. You can find the MediaTransportControls template in generic.xaml by searching for "MediaTransportControls".
 
 In the following sections, you learn how to customize several of the main elements of the transport controls:
 - [**Slider**](/uwp/api/Windows.UI.Xaml.Controls.Slider): allows a user to scrub through their media and also displays progress
@@ -85,7 +85,7 @@ If you want to modify only the appearance of the MediaTransportControls, you can
 </MediaPlayerElement>
 ```
 
-For more info about modifying styles and templates, see [Styling controls](../style/xaml-styles.md) and [Control templates](../style/xaml-control-templates.md).
+For more info about modifying styles and templates, see [Styling controls](../../develop/platform/xaml/xaml-styles.md) and [Control templates](../../develop/platform/xaml/xaml-control-templates.md).
 
 ### Create a derived control
 

hub/apps/design/controls/expander.md

@@ -235,7 +235,7 @@ private void Expander_Collapsed(muxc.Expander sender,
 
 ### Lightweight styling
 
-You can modify the default `Style` and `ControlTemplate` to give the control a unique appearance. See the Control Style and Template section of the Expander API docs for a list of the available theme resources. For more info, see the [Light-weight styling section](../style/xaml-styles.md#lightweight-styling) of the [Styling controls](../style/xaml-styles.md) article.
+You can modify the default `Style` and `ControlTemplate` to give the control a unique appearance. See the Control Style and Template section of the Expander API docs for a list of the available theme resources. For more info, see the [Light-weight styling section](../../develop/platform/xaml/xaml-styles.md#lightweight-styling) of the [Styling controls](../../develop/platform/xaml/xaml-styles.md) article.
 
 ## Recommendations
 

hub/apps/design/controls/index.md

@@ -28,7 +28,7 @@ General instructions and code examples for adding and styling controls in XAML a
       There are 3 key steps to adding controls to your app: Add a control to your app UI, set properties on the control, and add code to the control's event handlers so that it does something.</p>
     :::column-end:::
     :::column:::
-      <p><b><a href="../style/xaml-styles.md">Styling controls</a></b> <br/>
+      <p><b><a href="../../develop/platform/xaml/xaml-styles.md">Styling controls</a></b> <br/>
       You can customize the appearance of your apps in many ways by using the XAML framework. Styles let you set control properties and reuse those settings for a consistent appearance across multiple controls.</p>
     :::column-end:::
 :::row-end:::

hub/apps/design/controls/infobar.md

@@ -298,8 +298,8 @@ XAML content can be added to an InfoBar using the Content property. It will appe
 You can modify the default Style and ControlTemplate to give the control a unique appearance.
 See the [Control Style and Template](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.infobar#control-style-and-template) section of the InfoBar API docs for a list of the available theme resources.
 
-For more info, see the [Light-weight styling section](../style/xaml-styles.md#lightweight-styling)
-of the [Styling controls](../style/xaml-styles.md)
+For more info, see the [Light-weight styling section](../../develop/platform/xaml/xaml-styles.md#lightweight-styling)
+of the [Styling controls](../../develop/platform/xaml/xaml-styles.md)
 article.
 
 For example, the following causes the background color for all informational InfoBars on a page to be blue: