aboutsummaryrefslogtreecommitdiff
path: root/website/README.md
diff options
context:
space:
mode:
authorOgulcan Celik <ogulcancelik@gmail.com>2026-07-22 14:58:26 +0300
committerOgulcan Celik <ogulcancelik@gmail.com>2026-07-22 14:59:09 +0300
commitc234f221f9be698bc0501c60459e1ae8e67df6c3 (patch)
tree944b4dec10fada8d93456dc5a85e6bfdb36a8b8b /website/README.md
parentef85fa0c7ebb48bb59fe7593af5a67f3e02ff3d4 (diff)
feat(docs): publish versioned release documentation
Diffstat (limited to 'website/README.md')
-rw-r--r--website/README.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/website/README.md b/website/README.md
index 36dfb12d..fd8d8ea2 100644
--- a/website/README.md
+++ b/website/README.md
@@ -9,3 +9,13 @@ bun run build
```
The build output is `dist/`. Configure Cloudflare Pages to use `website` as the project root and publish `dist`.
+
+Stable docs live in `src/content/docs/`. Unreleased docs live in `../docs/next/website/src/content/docs/` and are generated at `/docs/preview/`. Immutable release snapshots live in `../docs/versions/` and are generated at `/docs/<version>/`.
+
+Do not promote docs manually before a release. After the GitHub Release succeeds, release CI runs:
+
+```bash
+node website/scripts/docs-versions.mjs publish <tag>
+```
+
+This snapshots the tagged next docs and promotes the same tagged content to stable before the website deploy. Use `node website/scripts/docs-versions.mjs check` to validate committed snapshots against their release tags.