deduplicate dashboard (#5664)

* del: dashboard content and point to aspire.dev

* fix: Update dashboard links to use the new aspire.dev URLs

Author: IEvangelist

.github/dependabot.yml

@@ -272,39 +272,6 @@ updates:
       dotnet:
         patterns:
           - "*" # Prefer a single PR per solution update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard" #aspire-dashboard.sln
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for solutions.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per solution update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/BrowserTelemetry" #BrowserTelemetry.sln
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for solutions.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per solution update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/DisableAI/AspireApp" #AspireApp.sln
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for solutions.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per solution update.
   - package-ecosystem: "nuget"
     directory: "/docs/fundamentals/snippets/build-container-images" #build-container-images.sln
     schedule:
@@ -1163,116 +1130,6 @@ updates:
       dotnet:
         patterns:
           - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard/Aspire.Dashboard.ScreenCapture" #Aspire.Dashboard.ScreenCapture.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard/AspireSample/AspireSample.ApiService" #AspireSample.ApiService.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard/AspireSample/AspireSample.AppHost" #AspireSample.AppHost.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard/AspireSample/AspireSample.ServiceDefaults" #AspireSample.ServiceDefaults.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/automation/aspire-dashboard/AspireSample/AspireSample.Web" #AspireSample.Web.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/BrowserTelemetry/BrowserTelemetry.AppHost" #BrowserTelemetry.AppHost.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/BrowserTelemetry/BrowserTelemetry.ServiceDefaults" #BrowserTelemetry.ServiceDefaults.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/DisableAI/AspireApp/AspireApp.AppHost" #AspireApp.AppHost.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/DisableAI/AspireApp/AspireApp.ServiceDefaults" #AspireApp.ServiceDefaults.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/fundamentals/dashboard/snippets/DisableAI/AspireApp/AspireApp.Web" #AspireApp.Web.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
   - package-ecosystem: "nuget"
     directory: "/docs/fundamentals/snippets/annotations-overview" #annotations-overview.csproj
     schedule:

.openpublishing.redirection.json

@@ -343,6 +343,50 @@
     {
       "source_path_from_root": "/docs/get-started/upgrade-to-aspire-9.md",
       "redirect_url": "/dotnet/aspire/get-started/upgrade-to-aspire-13"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/overview.md",
+      "redirect_url": "https://aspire.dev/dashboard/overview/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/explore.md",
+      "redirect_url": "https://aspire.dev/dashboard/explore/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/copilot.md",
+      "redirect_url": "https://aspire.dev/dashboard/copilot/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/mcp-server.md",
+      "redirect_url": "https://aspire.dev/dashboard/mcp-server/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/standalone.md",
+      "redirect_url": "https://aspire.dev/dashboard/standalone/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/standalone-for-python.md",
+      "redirect_url": "https://aspire.dev/dashboard/standalone-for-python/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/standalone-for-nodejs.md",
+      "redirect_url": "https://aspire.dev/dashboard/standalone-for-nodejs/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/configuration.md",
+      "redirect_url": "https://aspire.dev/dashboard/configuration/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/security-considerations.md",
+      "redirect_url": "https://aspire.dev/dashboard/security-considerations/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/enable-browser-telemetry.md",
+      "redirect_url": "https://aspire.dev/dashboard/enable-browser-telemetry/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/dashboard/microsoft-collected-dashboard-telemetry.md",
+      "redirect_url": "https://aspire.dev/dashboard/microsoft-collected-dashboard-telemetry/"
     }
   ]
 }

docs/app-host/configuration.md

@@ -12,7 +12,7 @@ The AppHost project configures and starts your distributed application (<xref:As
 Configuration includes:
 
 - Settings for hosting the resource service, such as the address and authentication options.
-- Settings used to start the [Aspire dashboard](../fundamentals/dashboard/overview.md), such the dashboard's frontend and OpenTelemetry Protocol (OTLP) addresses.
+- Settings used to start the [Aspire dashboard](https://aspire.dev/dashboard/overview/), such the dashboard's frontend and OpenTelemetry Protocol (OTLP) addresses.
 - Internal settings that Aspire uses to run the AppHost. These are set internally but can be accessed by integrations that extend Aspire.
 
 AppHost configuration is provided by the AppHost launch profile. The AppHost has a launch settings file call _launchSettings.json_ which has a list of launch profiles. Each launch profile is a collection of related options which defines how you would like `dotnet` to start your application.
@@ -47,7 +47,7 @@ The preceding launch settings file:
 For more information, see [Aspire and launch profiles](../fundamentals/launch-profiles.md).
 
 > [!NOTE]
-> Configuration described on this page is for Aspire AppHost project. To configure the standalone dashboard, see [dashboard configuration](../fundamentals/dashboard/configuration.md).
+> Configuration described on this page is for Aspire AppHost project. To configure the standalone dashboard, see [dashboard configuration](https://aspire.dev/dashboard/configuration/).
 
 ## Common configuration
 
@@ -83,7 +83,7 @@ A resource service is hosted by the AppHost. The resource service is used by the
 
 ## Dashboard
 
-By default, the dashboard is automatically started by the AppHost. The dashboard supports [its own set of configuration](../fundamentals/dashboard/configuration.md), and some settings can be configured from the AppHost.
+By default, the dashboard is automatically started by the AppHost. The dashboard supports [its own set of configuration](https://aspire.dev/dashboard/configuration/), and some settings can be configured from the AppHost.
 
 | Option | Default value | Description |
 |--|--|--|
@@ -93,8 +93,8 @@ By default, the dashboard is automatically started by the AppHost. The dashboard
 | `ASPIRE_DASHBOARD_OTLP_HTTP_ENDPOINT_URL` | `null` | Configures the dashboard OTLP HTTP address. Used by the dashboard to receive telemetry over OTLP. If only `ASPIRE_DASHBOARD_OTLP_HTTP_ENDPOINT_URL` is configured then it is set on resources as the `OTEL_EXPORTER_OTLP_ENDPOINT` env var. The `OTEL_EXPORTER_OTLP_PROTOCOL` env var is `http/protobuf`. |
 | `ASPIRE_DASHBOARD_CORS_ALLOWED_ORIGINS` | `null` | Overrides the CORS allowed origins configured in the dashboard. This setting replaces the default behavior of calculating allowed origins based on resource endpoints. |
 | `ASPIRE_DASHBOARD_FRONTEND_BROWSERTOKEN` | Automatically generated 128-bit entropy token. | Configures the frontend browser token. This is the value that must be entered to access the dashboard when the auth mode is BrowserToken. If no browser token is specified then a new token is generated each time the AppHost is launched. |
-| `ASPIRE_DASHBOARD_TELEMETRY_OPTOUT` | `false` | Configures the dashboard to never send [usage telemetry](../fundamentals/dashboard/microsoft-collected-dashboard-telemetry.md). |
-| `ASPIRE_DASHBOARD_AI_DISABLED` | `false` | [GitHub Copilot in the dashboard](../fundamentals/dashboard/copilot.md) is available when the AppHost is launched by a supported IDE. When set to `true` Copilot is disabled in the dashboard and no Copilot UI is visible. |
+| `ASPIRE_DASHBOARD_TELEMETRY_OPTOUT` | `false` | Configures the dashboard to never send [usage telemetry](https://aspire.dev/dashboard/microsoft-collected-dashboard-telemetry/). |
+| `ASPIRE_DASHBOARD_AI_DISABLED` | `false` | [GitHub Copilot in the dashboard](https://aspire.dev/dashboard/copilot/) is available when the AppHost is launched by a supported IDE. When set to `true` Copilot is disabled in the dashboard and no Copilot UI is visible. |
 | `ASPIRE_DASHBOARD_FORWARDEDHEADERS_ENABLED` | `false` | Enables the Forwarded headers middleware that replaces the scheme and host values on the Request context with the values coming from the `X-Forwarded-Proto` and `X-Forwarded-Host` headers. |
 
 ## Internal

docs/architecture/overview.md

@@ -171,25 +171,25 @@ For more information on container networking, see [How container networks are ma
 
 ## Developer dashboard
 
-The [Aspire developer dashboard](../fundamentals/dashboard/overview.md) is a powerful tool designed to simplify local development and resource management. It also supports a [standalone mode](../fundamentals/dashboard/standalone.md) and integrates seamlessly when publishing to Azure Container Apps. With its intuitive interface, the dashboard empowers developers to monitor, manage, and interact with application resources effortlessly.
+The [Aspire developer dashboard](https://aspire.dev/dashboard/overview/) is a powerful tool designed to simplify local development and resource management. It also supports a [standalone mode](https://aspire.dev/dashboard/standalone/) and integrates seamlessly when publishing to Azure Container Apps. With its intuitive interface, the dashboard empowers developers to monitor, manage, and interact with application resources effortlessly.
 
 ### Monitor and manage resources
 
 The dashboard provides a user-friendly interface for inspecting resource states, viewing logs, and executing commands. Whether you're debugging locally or deploying to the cloud, the dashboard ensures you have full visibility into your application's behavior.
 
 ### Built-in and custom commands
 
-The dashboard provides a set of commands for managing resources, such as start, stop, and restart. While commands appear as intuitive actions in the dashboard UI, under the hood, they operate by manipulating DCP objects. For more information, see [Stop or Start a resource](../fundamentals/dashboard/explore.md#stop-or-start-a-resource).
+The dashboard provides a set of commands for managing resources, such as start, stop, and restart. While commands appear as intuitive actions in the dashboard UI, under the hood, they operate by manipulating DCP objects. For more information, see [Stop or Start a resource](https://aspire.dev/dashboard/explore/#stop-or-start-a-resource).
 
 In addition to these built-in commands, you can define custom commands tailored to your application's needs. These custom commands are registered in the app model and seamlessly integrated into the dashboard, providing enhanced flexibility and control. Learn more about custom commands in [Custom resource commands in Aspire](../fundamentals/custom-resource-commands.md).
 
 ### Real-time log streaming
 
-Stay informed with the dashboard's [real-time log streaming](../fundamentals/dashboard/explore.md#console-logs-page) feature. Logs from all resources in your app model are streamed from DCP to the AppHost and displayed in the dashboard. With advanced filtering options—by resource type, severity, and more—you can quickly pinpoint relevant information and troubleshoot effectively.
+Stay informed with the dashboard's [real-time log streaming](https://aspire.dev/dashboard/explore/#console-logs-page) feature. Logs from all resources in your app model are streamed from DCP to the AppHost and displayed in the dashboard. With advanced filtering options—by resource type, severity, and more—you can quickly pinpoint relevant information and troubleshoot effectively.
 
 The developer dashboard is more than just a tool—it's your command center for building, debugging, and managing Aspire applications with confidence and ease.
 
 ## See also
 
 - [Orchestration overview](../fundamentals/app-host-overview.md)
-- [Explore the Aspire dashboard](../fundamentals/dashboard/explore.md)
+- [Explore the Aspire dashboard](https://aspire.dev/dashboard/explore/)

docs/azure/configure-aca-environments.md

@@ -40,7 +40,7 @@ This module configures:
 - An Azure Container Registry (ACR) for the ACA environment.
 - A Log Analytics workspace for the ACA environment.
 - An Azure Container Apps environment.
-- The [Aspire dashboard](../fundamentals/dashboard/overview.md) for the ACA environment.
+- The [Aspire dashboard](https://aspire.dev/dashboard/overview/) for the ACA environment.
 - A role assignment for the user principal ID to the ACA environment.
 - Various outputs for the ACA environment.
 

docs/azure/integrations-overview.md

@@ -280,7 +280,7 @@ The preceding code:
 - Adds a project named `api` to the builder.
 - The `api` project references the `storage` resource regardless of the mode.
 
-The consuming API project uses the connection string information with no knowledge of how the AppHost configured it. In "publish" mode, the code adds a new Azure Storage resource—which would be reflected in the [deployment manifest](../deployment/manifest-format.md) accordingly. When in "run" mode the connection string corresponds to a configuration value visible to the AppHost. It's assumed that all role assignments for the target resource are configured. This means, you'd likely configure an environment variable or a user secret to store the connection string. The configuration is resolved from the `ConnectionStrings__storage` (or `ConnectionStrings:storage`) configuration key. These configuration values can be viewed when the app runs. For more information, see [Resource details](../fundamentals/dashboard/explore.md#resource-details).
+The consuming API project uses the connection string information with no knowledge of how the AppHost configured it. In "publish" mode, the code adds a new Azure Storage resource—which would be reflected in the [deployment manifest](../deployment/manifest-format.md) accordingly. When in "run" mode the connection string corresponds to a configuration value visible to the AppHost. It's assumed that all role assignments for the target resource are configured. This means, you'd likely configure an environment variable or a user secret to store the connection string. ...e the connection string corresponds to a configuration value visible to the AppHost. It's assumed that all role assignments for the target resource are configured. This means, you'd likely configure an environment variable or a user secret to store the connection string. The configuration is resolved from the `ConnectionStrings__storage` (or `ConnectionStrings:storage`) configuration key. These configuration values can be viewed when the app runs. For more information, see [Resource details](https://aspire.dev/dashboard/explore/#resource-details).
 
 Unlike existing resources modeled with [the first-class `AsExisting` API](#use-existing-azure-resources), existing resource modeled as connection strings can't be enhanced with additional role assignments or infrastructure customizations.
 

docs/azure/local-provisioning.md

@@ -155,7 +155,7 @@ This opens a dialog where you can configure the Azure provisioning settings, as
 
 ### Configuration prompts and error handling
 
-When the `Azure` configuration section is missing, has missing values, or is invalid, the [Aspire dashboard](../fundamentals/dashboard/overview.md) provides interactive prompts to help you configure the required values. The dashboard displays a message bar prompting you to **Enter values** for the missing configuration.
+When the `Azure` configuration section is missing, has missing values, or is invalid, the [Aspire dashboard](https://aspire.dev/dashboard/overview/) provides interactive prompts to help you configure the required values. The dashboard displays a message bar prompting you to **Enter values** for the missing configuration.
 
 If you dismiss the prompt or there are validation errors, the dashboard provides detailed error information. For example, consider an AppHost that's missing the `SubscriptionId` configuration value that's attempting to use an Azure Key Vault resource. The **Resources** page indicates the **State** as **Missing subscription configuration**: