From 334f750f6261dfcf5f669bd216f74344b7358830 Mon Sep 17 00:00:00 2001 From: Adam Date: Mon, 10 Aug 2026 00:13:22 +1000 Subject: [PATCH] docs: refresh the README after the repo import MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - The local-preview snippet told you to cd into a "privacycommand website" folder. That nesting was flattened when the site was imported into git; the content is at the repository root. - Added the intended hostname and a pointer to the new docs site, so the boundary between marketing copy and product documentation is stated. - The go-live checklist asked you to confirm the docs/RELEASES.md link in legal.html "once the doc is in the repo". It never was — that path does not exist in privacycommand and never has. Points at the real release workflow instead. --- README.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 095fa4c..9c3e480 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,14 @@ Marketing site for [privacycommand](https://github.com/privacykey/privacycommand) — the macOS forensic permission auditor in the privacykey family. Scaffolded from the privacytracker site so the two products feel like part of the same family. -Single-file static site. No framework, no build step. Drop the folder onto any static host (Netlify, Cloudflare Pages, GitHub Pages, S3 + CloudFront). +Static HTML. No framework, no build step. Point any static host at the +repository root (Netlify, Cloudflare Pages, GitHub Pages, S3 + CloudFront). + +**Hostname:** `privacycommand.privacykey.org` *(DNS not configured yet)* + +Full product documentation lives separately, at +[docs-privacycommand](https://github.com/privacykey/docs-privacycommand) → +`docs.privacycommand.privacykey.org`. Keep feature claims here in step with it. ## Layout @@ -41,7 +48,6 @@ Single-file static site. No framework, no build step. Drop the folder onto any s Anything that serves files works: ```sh -cd "privacycommand website" python3 -m http.server 4000 # open http://localhost:4000 ``` @@ -55,7 +61,7 @@ python3 -m http.server 4000 3. **Domain** — every canonical URL and OG tag points at `https://privacycommand.privacykey.org/`. Change the host if you ship under a different domain. 4. **`security.txt` `Expires`** — bump the date once a year. 5. **`sitemap.xml` `lastmod`** — bump on material changes. -6. **`docs/RELEASES.md` link** referenced in `legal.html` — confirm it resolves once the doc is in the repo. +6. **`docs/RELEASES.md` link** referenced in `legal.html` — that file does not exist in the privacycommand repo and never has. Point it at the release workflow instead: [`.github/workflows/release.yml`](https://github.com/privacykey/privacycommand/blob/main/.github/workflows/release.yml), which calls the shared pipeline in [privacykey/gh-workflows](https://github.com/privacykey/gh-workflows). ## Privacy posture (mirrored from the app)