docs: publish the site at stratara.tech

[yesbert]

⚠️ Do not merge before the DNS change

Merging this deploys a CNAME of stratara.tech. GitHub Pages then makes that the custom domain — and if the apex still resolves to the Plesk server, Pages cannot verify it, the certificate is not issued, and the site is reachable at neither host until DNS catches up. DNS first, merge second.

What has to happen at antagus.de

1. Replace the apex A record for stratara.tech (currently 217.154.79.173, the Plesk server) with GitHub's four:

   185.199.108.153
   185.199.109.153
   185.199.110.153
   185.199.111.153
   

   Optionally the AAAA records as well: 2606:50c0:8000::153, 8001::153, 8002::153, 8003::153.

2. Leave the docs record alone. docs.stratara.tech must keep pointing at yesbert.github.io: Pages redirects a previous custom domain to the current one only while that record still resolves to Pages. Deleting it turns every published link — the dev.to articles, the package READMEs already on nuget.org — into a dead end.

3. sonar.stratara.tech is a separate record and is untouched.

After merging, Pages provisions the certificate; that takes anywhere from a minute to an hour, and Enforce HTTPS may need switching back on once it is issued. The Plesk vhost for stratara.tech then receives no traffic — worth parking in Plesk so its Let's Encrypt renewals stop failing against a domain it no longer answers for.

What this changes

• docs/CNAME → stratara.tech, and _appBaseUrl with it, so canonical URLs follow.
• 33 references across README.md, llms.txt, SUPPORT.md, CONTRIBUTING.md, both issue templates and the two hero-sample READMEs.
• The docs.yml header now records why the old DNS record has to stay.

Two references are deliberately left pointing at the old host: the link in the released 4.0.2 changelog entry and the archived give-every-reader-their-door change. Both are dated records of what was true when written, and the redirect keeps them working.

How it was verified

• Local gauntlet green (./scripts/local-gauntlet.sh)
• docfx build --warningsAsErrors — 0 warnings, 0 errors

[Copilot]

🔵 Needs a closer look

Merge safety depends on an external DNS cutover timing that can’t be validated from the code changes alone.

Pull request overview

This PR migrates the project’s documentation site canonical host from docs.stratara.tech to the apex domain stratara.tech, aligning DocFX configuration and repository references with the GitHub Pages custom-domain setup described in the PR.

Changes:

• Switch GitHub Pages custom domain by updating docs/CNAME to stratara.tech and updating DocFX _appBaseUrl accordingly.
• Update repository-facing links (root README, support/contributing docs, llms.txt, issue templates, and sample READMEs) to point at https://stratara.tech.
• Document the DNS/redirect constraint in the docs deployment workflow header comments to prevent accidental removal of the old docs DNS record.

File summaries

File	Description
SUPPORT.md	Updates the canonical documentation link to https://stratara.tech.
samples/Stratara.Sample.TamperProof/README.md	Updates concept-doc link to the new docs host.
samples/Stratara.Sample.Encryption/README.md	Updates concept-doc link to the new docs host.
README.md	Updates primary documentation links (glossary, getting started, guides, concepts, samples) to https://stratara.tech.
llms.txt	Updates “Documentation site” and concept/guide links to https://stratara.tech.
docs/legal/privacy.md	Updates front-matter description to reference stratara.tech.
docs/docfx.json	Updates DocFX _appBaseUrl to https://stratara.tech for canonical URLs.
docs/CNAME	Sets GitHub Pages custom domain to stratara.tech.
CONTRIBUTING.md	Updates the “check the docs first” link to https://stratara.tech.
.github/workflows/docs.yml	Updates header comment to reflect new published host and keep-old-DNS-record requirement.
.github/ISSUE_TEMPLATE/question.md	Updates “checked documentation” checkbox link to https://stratara.tech.
.github/ISSUE_TEMPLATE/config.yml	Updates the documentation contact link URL to https://stratara.tech.

Review details

• Files reviewed: 12/12 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.