docs: the site now deploys as a Docker image

README gets a Deploying section; the deployment guide no longer says this site is on GitHub Pages. The Pages workflow stays there as an example.

Author: Shewart

README.md

@@ -78,7 +78,16 @@ Components/
 
 ## Framework version
 
-The site references `ShellDocs.* 0.1.17-alpha`. On a new release, bump the four package versions in `ShellDocs.Site.csproj` and the CLI version pinned in `.github/workflows/deploy-pages.yml` together.
+The site references `ShellDocs.* 0.1.17-alpha`. On a new release, bump the four package versions in `ShellDocs.Site.csproj` together.
+
+## Deploying
+
+The site runs as a Docker image (`Dockerfile`). `.github/workflows/docker.yml` builds it on every pull request, and on every push to `main` pushes it to `docker.zuluville.com/shelldocs-docs` as `:latest` and `:<short commit>`. Registry login uses the repository secrets `REGISTRY_USERNAME` and `REGISTRY_PASSWORD`.
+
+```bash
+docker build -t docker.zuluville.com/shelldocs-docs .
+docker run --rm -p 8080:8080 docker.zuluville.com/shelldocs-docs
+```
 
 ## License
 

content/docs/guides/deployment.md

@@ -6,7 +6,7 @@ order: 7
 
 # Deployment
 
-A ShellDocs site is a Blazor Web App. You can run it on a .NET host, or export it to static files with `shelldocs build` and serve those from any static host. This site is a static export on GitHub Pages.
+A ShellDocs site is a Blazor Web App. You can run it on a .NET host, or export it to static files with `shelldocs build` and serve those from any static host. This site runs on a .NET host, as a Docker image.
 
 ## Choosing
 
@@ -60,7 +60,7 @@ The output goes to `./publish`. Every flag is covered in [shelldocs build](/docs
 
 ## GitHub Pages
 
-This is the workflow this site deploys with. It builds on every push to `main` and can be run by hand.
+This workflow builds on every push to `main` and can be run by hand.
 
 ```yaml
 name: Deploy to GitHub Pages