Adapt the deploy workflow for other hosts

Lock in the four shared values

Every host configuration shares four knobs: the build command (dotnet run --project <your-project> -- build "$BASE_URL"), the publish directory (output/, the default from OutputOptions), the .NET SDK pin (11.0.x, matching setup-dotnet@v4 in the GitHub Pages workflow), and the base URL (/ for apex domains, /<path> for sub-path hosting). Settle on these four values before opening any host dashboard — the per-host files below are each those same four values expressed in that host's syntax. See CLI and build arguments for the OutputOptions.FromArgs grammar.

Pick your host and copy the per-host deltas

The table below is the authoritative diff against the GitHub Pages workflow — blank cells mean nothing changes from the canonical recipe. Find the row for the target host, then continue to the matching step for the host-specific config file.

Azure Static Web Apps — drop in staticwebapp.config.json

Commit the JSON below at the repo root; SWA reads it during deploy and applies routes, MIME overrides, nav fallback, and 404 handling. In the SWA workflow (.github/workflows/azure-static-web-apps-<id>.yml, generated by the Azure portal), confirm app_build_command is dotnet run --project <your-project> -- build and output_location is output — everything else from the canonical GitHub Pages workflow applies unchanged.

{
  "$schema": "https://json.schemastore.org/staticwebapp.config.json",
  "trailingSlash": "auto",
  "mimeTypes": {
    ".json": "application/json",
    ".xml": "application/xml",
    ".webmanifest": "application/manifest+json"
  },
  "routes": [
    {
      "route": "/sitemap.xml",
      "headers": {
        "Cache-Control": "public, max-age=3600"
      }
    },
    {
      "route": "/llms.txt",
      "headers": {
        "Cache-Control": "public, max-age=3600"
      }
    },
    {
      "route": "/_content/*",
      "headers": {
        "Cache-Control": "public, max-age=31536000, immutable"
      }
    }
  ],
  "navigationFallback": {
    "rewrite": "/404.html",
    "exclude": [
      "/_content/*",
      "/_spa-data/*",
      "/*.{css,js,json,png,jpg,jpeg,gif,svg,webp,ico,woff,woff2,ttf,xml,txt,webmanifest}"
    ]
  },
  "responseOverrides": {
    "404": {
      "rewrite": "/404.html"
    }
  },
  "globalHeaders": {
    "X-Content-Type-Options": "nosniff",
    "Referrer-Policy": "strict-origin-when-cross-origin"
  }
}

Netlify — drop in netlify.toml

Commit the TOML below at the repo root; Netlify autodetects it and no dashboard build-setting changes are needed beyond linking the repo. BASE_URL defaults to / — override it in Site configuration → Environment variables for sub-path hosting. The [[redirects]] block with status = 404 routes deep-link misses to the generated output/404.html.

# Netlify configuration for a Pennington static site.
#
# Netlify serves `publish = "output"` verbatim. Set `BASE_URL` in the
# Netlify dashboard (Site configuration → Environment variables) if you
# need a sub-path; for a root-served site leave it as the default `/`.
#
# The 404 fallback uses Netlify's conditional `status = 404` rewrite so
# deep-link misses return the generated `output/404.html` page body
# instead of Netlify's default 404 shell.
  
[build]
  command = "dotnet run --project examples/SubPathDeployableExample -- build ${BASE_URL:-/}"
  publish = "output"
  
[build.environment]
  DOTNET_VERSION = "11.0.x"
  BASE_URL = "/"
  
[[headers]]
  for = "/_content/*"
  [headers.values]
    Cache-Control = "public, max-age=31536000, immutable"
  
[[headers]]
  for = "/*"
  [headers.values]
    X-Content-Type-Options = "nosniff"
    Referrer-Policy = "strict-origin-when-cross-origin"
  
# Pretty-URL fallback: Pennington's DocSite emits `<slug>/index.html`,
# which Netlify already serves at `/<slug>/`. The explicit 404 rule
# below only fires when nothing else matches.
[[redirects]]
  from = "/*"
  to = "/404.html"
  status = 404

Cloudflare Pages — configure in dashboard (no config file needed)

Cloudflare Pages has no first-party config file equivalent to SWA or Netlify, so everything goes in the project dashboard under Settings → Builds & deployments: set Build command to dotnet run --project <your-project> -- build, Build output directory to output, and add environment variables DOTNET_VERSION=11.0.x and BASE_URL=/ (or the relevant sub-path). For custom cache headers on /_content/*, drop a _headers file into wwwroot/ so it ships as part of output/ — the directive format matches the Netlify and Azure snippets above.

Pass the right baseUrl for the host's URL shape

GitHub Pages defaults to a sub-path; Azure Static Web Apps, Cloudflare Pages, and Netlify default to the apex — so the build argument is usually different. For apex deploys pass nothing (or /); for a sub-path pass /<path> and BaseUrlHtmlRewriter prefixes every internal href, src, and action on the way out. Full details are in Host under a sub-path (base URL).