Reorganize Blazor Host and Deploy node (#35098)

Author: guardrex

.openpublishing.redirection.json

@@ -972,12 +972,12 @@
         },
         {
             "source_path": "aspnetcore/host-and-deploy/blazor/client-side.md",
-            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/",
             "redirect_document_id": false
         },
         {
             "source_path": "aspnetcore/host-and-deploy/blazor/server-side.md",
-            "redirect_url": "/aspnet/core/blazor/host-and-deploy/server",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/server/",
             "redirect_document_id": false
         },
         {
@@ -1077,12 +1077,12 @@
         },
         {
             "source_path": "aspnetcore/host-and-deploy/blazor/server.md",
-            "redirect_url": "/aspnet/core/blazor/host-and-deploy/server",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/server/",
             "redirect_document_id": false
         },
         {
             "source_path": "aspnetcore/host-and-deploy/blazor/webassembly.md",
-            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/",
             "redirect_document_id": false
         },
         {
@@ -1310,7 +1310,7 @@
         },
         {
             "source_path": "aspnetcore/blazor/http-caching-issues.md",
-            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly-caching/http-caching-issues",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/http-caching-issues",
             "redirect_document_id": false
         },
         {
@@ -1357,6 +1357,36 @@
             "source_path": "aspnetcore/blazor/security/server/index.md",
             "redirect_url": "/aspnet/core/blazor/security/",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly-caching/index.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/runtime-and-app-bundle-caching",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly-caching/http-caching-issues.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/http-caching-issues",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/multiple-hosted-webassembly.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/multiple-hosted-webassembly",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/webassembly-deployment-layout.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/deployment-layout",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/host-and-deploy/server.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/server/",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/components/class-libraries.md

@@ -340,7 +340,7 @@ For more information, see <xref:razor-pages/ui-class#create-an-rcl-with-static-a
 
 ## Supply components and static assets to multiple hosted Blazor apps
 
-For more information, see <xref:blazor/host-and-deploy/multiple-hosted-webassembly>.
+For more information, see <xref:blazor/host-and-deploy/webassembly/multiple-hosted-webassembly>.
 
 :::moniker-end
 

aspnetcore/blazor/components/index.md

@@ -1684,7 +1684,7 @@ Use a base-relative path (`/`) to refer to the web root for a static asset. In t
 
 Components do **not** support tilde-slash notation (`~/`).
 
-For information on setting an app's base path, see <xref:blazor/host-and-deploy/index#app-base-path>.
+For information on setting an app's base path, see <xref:blazor/host-and-deploy/app-base-path>.
 
 ## Tag Helpers aren't supported in components
 

aspnetcore/blazor/components/integration-hosted-webassembly.md

@@ -559,7 +559,7 @@ The persisted prerendered state is transferred to the client, where it's used to
 * Authentication and authorization subjects that pertain to prerendering
   * [General aspects](xref:blazor/security/index)
   * [Prerendering with authentication in hosted Blazor WebAssembly apps](xref:blazor/security/webassembly/additional-scenarios#prerendering-with-authentication)
-* [Host and deploy: Blazor WebAssembly](xref:blazor/host-and-deploy/webassembly)
+* <xref:blazor/host-and-deploy/webassembly/index>
 * [Handle errors: Prerendering](xref:blazor/fundamentals/handle-errors#prerendering)
 * <xref:Microsoft.AspNetCore.Components.Routing.Router.OnNavigateAsync> is executed *twice* when prerendering: [Handle asynchronous navigation events with `OnNavigateAsync`](xref:blazor/fundamentals/routing#handle-asynchronous-navigation-events-with-onnavigateasync)
 
@@ -1074,7 +1074,7 @@ The persisted prerendered state is transferred to the client, where it's used to
 * Authentication and authorization subjects that pertain to prerendering
   * [General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
   * [Prerendering with authentication](xref:blazor/security/webassembly/additional-scenarios#prerendering-with-authentication)
-* [Host and deploy: Blazor WebAssembly](xref:blazor/host-and-deploy/webassembly)
+* <xref:blazor/host-and-deploy/webassembly/index>
 
 :::moniker-end
 
@@ -1332,7 +1332,7 @@ Additional work might be required depending on the static resources that compone
 * Authentication and authorization subjects that pertain to prerendering
   * [General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
   * [Prerendering with authentication](xref:blazor/security/webassembly/additional-scenarios#prerendering-with-authentication)
-* [Host and deploy: Blazor WebAssembly](xref:blazor/host-and-deploy/webassembly)
+* <xref:blazor/host-and-deploy/webassembly/index>
 
 :::moniker-end
 

aspnetcore/blazor/components/integration.md

@@ -58,7 +58,7 @@ Use the following guidance to integrate Razor components into pages or views of
          render-mode="ServerPrerendered" />
      ```
 
-     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, follow the guidance in the *App base path* section of the <xref:blazor/host-and-deploy/index#app-base-path> article.
+     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, see <xref:blazor/host-and-deploy/app-base-path>.
 
      The <xref:Microsoft.AspNetCore.Components.Web.HeadOutlet> component is used to render head (`<head>`) content for page titles (<xref:Microsoft.AspNetCore.Components.Web.PageTitle> component) and other head elements (<xref:Microsoft.AspNetCore.Components.Web.HeadContent> component) set by Razor components. For more information, see <xref:blazor/components/control-head-content>.
 
@@ -556,7 +556,7 @@ To resolve the problem, use ***either*** of the following approaches:
   * [Prerendering with JavaScript interop](xref:blazor/components/lifecycle#prerendering-with-javascript-interop)
 * [Authentication and authorization: General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
 * [Handle Errors: Prerendering](xref:blazor/fundamentals/handle-errors#prerendering)
-* [Host and deploy: Blazor Server](xref:blazor/host-and-deploy/server)
+* <xref:blazor/host-and-deploy/server/index>
 * [Threat mitigation: Cross-site scripting (XSS)](xref:blazor/security/interactive-server-side-rendering#cross-site-scripting-xss)
 * <xref:Microsoft.AspNetCore.Components.Routing.Router.OnNavigateAsync> is executed *twice* when prerendering: [Handle asynchronous navigation events with `OnNavigateAsync`](xref:blazor/fundamentals/routing#handle-asynchronous-navigation-events-with-onnavigateasync)
 
@@ -589,7 +589,7 @@ Use the following guidance to integrate Razor components into pages or views of
      <component type="typeof(HeadOutlet)" render-mode="ServerPrerendered" />
      ```
 
-     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, follow the guidance in the *App base path* section of the <xref:blazor/host-and-deploy/index#app-base-path> article.
+     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, see <xref:blazor/host-and-deploy/app-base-path>.
   
      The <xref:Microsoft.AspNetCore.Components.Web.HeadOutlet> component is used to render head (`<head>`) content for page titles (<xref:Microsoft.AspNetCore.Components.Web.PageTitle> component) and other head elements (<xref:Microsoft.AspNetCore.Components.Web.HeadContent> component) set by Razor components. For more information, see <xref:blazor/components/control-head-content>.
 
@@ -1075,7 +1075,7 @@ To resolve the problem, use ***either*** of the following approaches:
   * [Prerendering with JavaScript interop](xref:blazor/components/lifecycle#prerendering-with-javascript-interop)
 * [Authentication and authorization: General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
 * [Handle Errors: Prerendering](xref:blazor/fundamentals/handle-errors#prerendering)
-* [Host and deploy: Blazor Server](xref:blazor/host-and-deploy/server)
+* <xref:blazor/host-and-deploy/server/index>
 * [Threat mitigation: Cross-site scripting (XSS)](xref:blazor/security/interactive-server-side-rendering#cross-site-scripting-xss)
 
 :::moniker-end
@@ -1103,7 +1103,7 @@ An existing Razor Pages or MVC app can integrate Razor components into pages or
      <base href="~/" />
      ```
 
-     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, follow the guidance in the *App base path* section of the <xref:blazor/host-and-deploy/index#app-base-path> article.
+     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, see <xref:blazor/host-and-deploy/app-base-path>.
 
    * Add a `<script>` tag for the `blazor.server.js` script immediately before the `Scripts` render section.
 
@@ -1507,7 +1507,7 @@ To resolve the problem, use ***either*** of the following approaches:
   * [Prerendering with JavaScript interop](xref:blazor/components/lifecycle#prerendering-with-javascript-interop)
 * [Authentication and authorization: General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
 * [Handle Errors: Prerendering](xref:blazor/fundamentals/handle-errors#prerendering)
-* [Host and deploy: Blazor Server](xref:blazor/host-and-deploy/server)
+* <xref:blazor/host-and-deploy/server/index>
 * [Threat mitigation: Cross-site scripting (XSS)](xref:blazor/security/interactive-server-side-rendering#cross-site-scripting-xss)
 
 :::moniker-end
@@ -1537,7 +1537,7 @@ An existing Razor Pages or MVC app can integrate Razor components into pages or
      + <base href="~/" />
      ```
 
-     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, follow the guidance in the *App base path* section of the <xref:blazor/host-and-deploy/index#app-base-path> article.
+     The `href` value (the *app base path*) in the preceding example assumes that the app resides at the root URL path (`/`). If the app is a sub-application, see <xref:blazor/host-and-deploy/app-base-path>.
 
    * Add a `<script>` tag for the `blazor.server.js` script immediately before the `Scripts` render section.
 
@@ -1937,7 +1937,7 @@ To resolve the problem, use ***either*** of the following approaches:
   * [Prerendering with JavaScript interop](xref:blazor/components/lifecycle#prerendering-with-javascript-interop)
 * [Authentication and authorization: General aspects](xref:blazor/security/index#aspnet-core-blazor-authentication-and-authorization)
 * [Handle Errors: Prerendering](xref:blazor/fundamentals/handle-errors#prerendering)
-* [Host and deploy: Blazor Server](xref:blazor/host-and-deploy/server)
+* <xref:blazor/host-and-deploy/server/index>
 * [Threat mitigation: Cross-site scripting (XSS)](xref:blazor/security/interactive-server-side-rendering#cross-site-scripting-xss)
 
 :::moniker-end

aspnetcore/blazor/fundamentals/environments.md

@@ -151,7 +151,7 @@ In the following example for IIS, the custom header (`Blazor-Environment`) is ad
 ```
 
 > [!NOTE]
-> To use a custom `web.config` file for IIS that isn't overwritten when the app is published to the `publish` folder, see <xref:blazor/host-and-deploy/webassembly#use-a-custom-webconfig>.
+> To use a custom `web.config` file for IIS that isn't overwritten when the app is published to the `publish` folder, see <xref:blazor/host-and-deploy/webassembly/iis#use-of-a-custom-webconfig>.
 
 ### Nginx
 
@@ -172,7 +172,7 @@ http {
 For more information, see the following resources:
 
 * [Nginx documentation](http://nginx.org/docs/http/ngx_http_headers_module.html)
-* [Blazor WebAssembly Nginx hosting guidance](xref:blazor/host-and-deploy/webassembly#nginx)
+* <xref:blazor/host-and-deploy/webassembly/nginx>
 
 ### Apache
 
@@ -186,10 +186,10 @@ For Apache servers, use the `Header` directive from the `mod_headers` module:
 </VirtualHost>
 ```
 
-For more information:
+For more information, see the following resources:
 
 * [Apache documentation (search the latest release for "`mod_headers`")](https://httpd.apache.org/docs/)
-* [Blazor WebAssembly Apache hosting guidance](xref:blazor/host-and-deploy/webassembly#apache)
+* <xref:blazor/host-and-deploy/webassembly/apache>
 
 ## Set the environment for Azure App Service
 

aspnetcore/blazor/fundamentals/routing.md

@@ -99,7 +99,7 @@ Components support multiple route templates using multiple [`@page` directives](
 :::moniker-end
 
 > [!IMPORTANT]
-> For URLs to resolve correctly, the app must include a `<base>` tag ([location of `<head>` content](xref:blazor/project-structure#location-of-head-and-body-content)) with the app base path specified in the `href` attribute. For more information, see <xref:blazor/host-and-deploy/index#app-base-path>.
+> For URLs to resolve correctly, the app must include a `<base>` tag ([location of `<head>` content](xref:blazor/project-structure#location-of-head-and-body-content)) with the app base path specified in the `href` attribute. For more information, see <xref:blazor/host-and-deploy/app-base-path>.
 
 :::moniker range="< aspnetcore-6.0"
 
@@ -1818,6 +1818,6 @@ The typical configuration is to route all requests to a Razor page, which acts a
 
 The route specified in the host file is called a *fallback route* because it operates with a low priority in route matching. The fallback route is used when other routes don't match. This allows the app to use other controllers and pages without interfering with component routing in the Blazor Server app.
 
-For information on configuring <xref:Microsoft.AspNetCore.Builder.RazorPagesEndpointRouteBuilderExtensions.MapFallbackToPage%2A> for non-root URL server hosting, see <xref:blazor/host-and-deploy/index#app-base-path>.
+For information on configuring <xref:Microsoft.AspNetCore.Builder.RazorPagesEndpointRouteBuilderExtensions.MapFallbackToPage%2A> for non-root URL server hosting, see <xref:blazor/host-and-deploy/app-base-path>.
 
 :::moniker-end

aspnetcore/blazor/fundamentals/signalr.md

@@ -185,7 +185,7 @@ The following error is thrown by an app that hasn't enabled session affinity in
 
 > :::no-loc text="Uncaught (in promise) Error: Invocation canceled due to the underlying connection being closed.":::
 
-For more information on session affinity with Azure App Service hosting, see <xref:blazor/host-and-deploy/server#azure-app-service>.
+For more information on session affinity with Azure App Service hosting, see <xref:blazor/host-and-deploy/server/index#azure-app-service>.
 
 ## Azure SignalR Service
 
@@ -196,7 +196,7 @@ The service isn't required for Blazor apps hosted in Azure App Service or Azure
 * To facilitate connection scale out.
 * Handle global distribution.
 
-For more information, see <xref:blazor/host-and-deploy/server#azure-signalr-service>.
+For more information, see <xref:blazor/host-and-deploy/server/index#azure-signalr-service>.
 
 ## Server-side circuit handler options
 
@@ -297,7 +297,7 @@ services.AddServerSideBlazor().AddHubOptions(options =>
 >
 > Blazor relies on <xref:Microsoft.AspNetCore.SignalR.HubOptions.MaximumParallelInvocationsPerClient%2A> set to 1, which is the default value. For more information, see [MaximumParallelInvocationsPerClient > 1 breaks file upload in Blazor Server mode (`dotnet/aspnetcore` #53951)](https://github.com/dotnet/aspnetcore/issues/53951).
 
-For information on memory management, see <xref:blazor/host-and-deploy/server#memory-management>.
+For information on memory management, see <xref:blazor/host-and-deploy/server/memory-management>.
 
 ## Blazor hub options
 
@@ -993,8 +993,8 @@ When changing the values of the server timeout (<xref:Microsoft.AspNetCore.Signa
 
 For more information, see the *Global deployment and connection failures* sections of the following articles:
 
-* <xref:blazor/host-and-deploy/server#global-deployment-and-connection-failures>
-* <xref:blazor/host-and-deploy/webassembly#global-deployment-and-connection-failures>
+* <xref:blazor/host-and-deploy/server/index#global-deployment-and-connection-failures>
+* <xref:blazor/host-and-deploy/webassembly/index#global-deployment-and-connection-failures>
 
 ## Modify the server-side reconnection handler
 
@@ -1640,7 +1640,7 @@ In the preceding code, `NavManager` is a <xref:Microsoft.AspNetCore.Components.N
 
 ## Additional server-side resources
 
-* [Server-side host and deployment guidance: SignalR configuration](xref:blazor/host-and-deploy/server#signalr-configuration)
+* [Server-side host and deployment guidance: SignalR configuration](xref:blazor/host-and-deploy/server/index#signalr-configuration)
 * <xref:signalr/introduction>
 * <xref:signalr/configuration>
 * Server-side security documentation