Merge branch 'docs/auto-deploy' of bajdev/posts into main

README.md

@@ -99,14 +99,14 @@ a user-visible change. The git commit is added automatically at build time.
 
 ## Deployment
 
-Runs as systemd unit `goapp@posts` on port 8002 behind nginx. Deploy with:
+Runs as systemd unit `goapp@posts` on port 8002 behind nginx.
 
-```sh
-deploy-go posts --content
-```
+Merging a pull request into `main` deploys it automatically. The pipeline in
+[bajdev/devops](https://git.monoaf.com/bajdev/devops) builds the merge commit,
+syncs `content/` to `/opt/apps/posts/content/`, restarts the app, and tags
+the release `deploy/posts/<UTC time>`. There's no manual deploy step.
 
-which builds and installs the binary and syncs `content/` to
-`/opt/apps/posts/content/`.
+To roll back to an earlier release, see "Rollback" in the devops README.
 
 ## License
 

about.md

@@ -59,7 +59,7 @@ Its title is "A short note" and its date comes from the file name.
 ## Publishing
 
 Posts are reviewed like code: add the file on a branch, open a pull request,
-and the post goes live once it is merged and deployed. To hold a post back
+and the post goes live automatically about a minute after the merge. To hold a post back
 after merging, set `draft: true`.
 
 ## What Markdown works

content/2026-10-24-hello-world.md

@@ -65,7 +65,7 @@ Its title is "A short note" and its date comes from the file name.
 ## Publishing
 
 Posts are reviewed like code: add the file on a branch, open a pull request,
-and the post goes live once it is merged and deployed. To hold a post back
+and the post goes live automatically about a minute after the merge. To hold a post back
 after merging, set `draft: true`.
 
 ## What Markdown works