Deduping packaging content (#6565)

---------

Co-authored-by: Jim Walker <[email protected]>

Author: niels9001

.openpublishing.redirection.json

@@ -11082,17 +11082,17 @@
     },
     {
       "source_path": "hub/apps/how-tos/chatgpt-openai-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
       "source_path": "hub/apps/how-tos/copilot-chat-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
       "source_path": "hub/apps/how-tos/dall-e-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
@@ -11410,6 +11410,11 @@
       "redirect_url": "/windows/apps/dev-tools/visual-studio",
       "redirect_document_id": false
     },
+    {
+      "source_path": "hub/apps/package-and-deploy/choose-packaging-model.md",
+      "redirect_url": "/windows/apps/package-and-deploy/packaging/",
+      "redirect_document_id": false
+    },
     {
       "source_path": "hub/apps/design/globalizing/use-patterns-to-format-dates-and-times.md",
       "redirect_url": "/windows/apps/design/globalizing/use-global-ready-formats#use-templates-and-patterns-for-advanced-datetime-formatting",

hub/apps/dev-tools/winapp-cli/index.md

@@ -21,17 +21,7 @@ Whether you're building with .NET/Win32, CMake, Electron, or Rust, this CLI give
 
 ## Why package identity?
 
-Many powerful Windows APIs require your app to have package identity, enabling you to leverage OS components Windows offers that you wouldn't otherwise have access to. With identity, your app gains access to features like notifications, OS integration, and on-device AI.
-
-Examples of what package identity and MSIX packaging unlocks:
-
-- [Interactive native notifications](/windows/apps/develop/notifications/app-notifications/app-notifications-quickstart?tabs=cs) and notification management
-- [Integration with Windows Explorer, Taskbar, Share sheet](/windows/apps/develop/windows-integration/integrate-sharesheet-packaged), and other shell surfaces
-- [Protocol handlers](/windows/apps/desktop/modernize/desktop-to-uwp-extensions#start-your-application-in-different-ways) (`yourapp://` URIs)
-- [On-device AI](/windows/ai/apis/) (local LLM, text and image AI APIs)
-- [Background tasks](/windows/uwp/launch-resume/declare-background-tasks-in-the-application-manifest) (run when app is closed)
-- [File type associations](/windows/apps/desktop/modernize/desktop-to-uwp-extensions#integrate-with-file-explorer)
-- [Clean install/uninstall and auto-updates](/windows/msix/overview)
+Many powerful Windows APIs require your app to have package identity. With identity, your app gains access to features like notifications, OS integration, and on-device AI. For a full list of what package identity unlocks and help choosing the right packaging model, see [Packaging overview](../../package-and-deploy/packaging/index.md).
 
 ## Installation
 

hub/apps/get-started/start-here.md

@@ -69,9 +69,6 @@ In the Visual Studio Installer, select the following workloads on the **Workload
 
 2. Search for **WinUI**, select the **WinUI Blank App (Packaged)** C# project template, and select **Next**.
 
-   > [!NOTE]
-   > The **Packaged** template is recommended for new apps. A packaged app (using MSIX) gives your users a clean install and uninstall experience, and enables Windows features like notifications, background tasks, and the Microsoft Store. You can learn more about the packaged vs. unpackaged choice in [Windows apps: packaging, deployment, and process](intro-pack-dep-proc.md).
-
    :::image type="content" source="images/hello-world/create-project.png" lightbox="images/hello-world/create-project.png" alt-text="Blank, packaged WinUI C# desktop app":::
 
 3. Enter a project name and select **Create**.

hub/apps/package-and-deploy/choose-packaging-model.md

@@ -14,7 +14,7 @@ ms.localizationpriority: medium
 
 App packaging provides your application with a predictable installation, update, and servicing model on Windows. While WinUI 3 apps are packaged by default, many other types of apps aren't. And adding package identity unlocks a wide range of Windows capabilities. Features that depend on package identity to function include background tasks, notifications, live tiles, custom context menu extensions, share targets, and other extensibility points. Packaging also helps ensure cleaner deployments, reliable updates, and streamlined distribution through channels such as the Microsoft Store and enterprise deployment tools.
 
-Not sure which packaging model is right for your app? See [Choose a packaging model](choose-packaging-model.md).
+Not sure which packaging model is right for your app? See [Packaging overview](packaging/index.md).
 
 When deploying apps that use the Windows App SDK, you can choose between framework-dependent and self-contained deployment models. Framework-dependent apps rely on the Windows App SDK runtime and/or framework package being installed on the user’s machine. In contrast, self-contained apps bundle the Windows App SDK dependencies directly with the application, ensuring the app carries everything it needs to run. The right model depends on your distribution scenario, update strategy, and how much control you want over the app’s footprint and dependencies.