Revert "docs: publish the site at stratara.tech" - #56
Merged
Conversation
The apex has to keep pointing at the Plesk server: too much else depends on it. Pages decides which hostname it answers for from the CNAME file in the deployed artifact, not from the repository setting alone, so restoring the setting was not enough — the artifact had to be rebuilt with the old host. Deployment to that server over rsync comes next.
There was a problem hiding this comment.
🟢 Approval recommended
The changes consistently restore the docs hostname across build artifacts and repository-facing links, with only a minor README badge-text nit noted.
Pull request overview
This PR reverts the documentation site’s published hostname back to docs.stratara.tech (instead of the apex stratara.tech), aligning the DocFX build output, GitHub Pages CNAME, and repository-facing links with the intended DNS setup.
Changes:
- Restore GitHub Pages custom-domain artifact configuration via
docs/CNAMEand DocFX_appBaseUrltodocs.stratara.tech. - Update repo documentation and templates to link to
https://docs.stratara.tech(README, SUPPORT, CONTRIBUTING, issue templates, sample READMEs,llms.txt). - Adjust the docs deployment workflow commentary to reflect the restored docs hostname.
File summaries
| File | Description |
|---|---|
| SUPPORT.md | Updates the canonical docs link to https://docs.stratara.tech. |
| samples/Stratara.Sample.TamperProof/README.md | Updates concept-doc link to the restored docs hostname. |
| samples/Stratara.Sample.Encryption/README.md | Updates concept-doc link to the restored docs hostname. |
| README.md | Updates multiple documentation links to https://docs.stratara.tech. |
| llms.txt | Updates “authoritative reference” links to https://docs.stratara.tech. |
| docs/legal/privacy.md | Updates frontmatter description to reference docs.stratara.tech. |
| docs/docfx.json | Restores _appBaseUrl to https://docs.stratara.tech. |
| docs/CNAME | Restores the Pages custom-domain CNAME value to docs.stratara.tech. |
| CONTRIBUTING.md | Updates “check docs first” link to https://docs.stratara.tech. |
| .github/workflows/docs.yml | Updates workflow header comment to reflect the restored docs hostname. |
| .github/ISSUE_TEMPLATE/question.md | Updates pre-flight checklist to point at https://docs.stratara.tech. |
| .github/ISSUE_TEMPLATE/config.yml | Updates “Stratara documentation” contact link to https://docs.stratara.tech. |
Review details
- Files reviewed: 12/12 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The apex has to keep pointing at the Plesk server — too much else depends on it. The move is not abandoned, but it will be done by deploying to that server over rsync rather than by moving the domain to GitHub Pages.
What was learned, because it is not obvious
Restoring the Pages custom-domain setting to
docs.stratara.techdid not bring the site back: Pages decides which hostname it answers for from theCNAMEfile in the deployed artifact, not from the repository setting alone. Withstratara.techstill in the artifact,docs.stratara.techkept returning There isn't a GitHub Pages site here. The artifact has to be rebuilt, which is what merging this does.The mirror image of the same surprise happened on the way out: with the Actions-based deployment, the
CNAMEfile does not set the custom domain either — that was the old branch-publishing behaviour. Both halves have to be done, and in the right order.What this restores
docs/CNAME,_appBaseUrland 33 references acrossREADME.md,llms.txt,SUPPORT.md,CONTRIBUTING.md, both issue templates and the two hero-sample READMEs.The local badges from #54 are untouched — this reverts only the domain change.
How it was verified
docfx build --warningsAsErrors— 0 warnings, 0 errorsdocs/CNAMEreadsdocs.stratara.tech;docs/index.mdstill references the three local badges