Must be generated, not hand-maintained per release: release history already exists in CHANGELOG.archied.md and CHANGELOG.archie.md, produced by tools/release.sh from conventional commits; tags are archied/vX.Y.Z and archie/vX.Y.Z. mkdocs.yml holds back archive/, inspiration/, prds/*, github-token.md; everything else under docs/ is public. task docs:site is mkdocs build --strict, so a dead internal link fails the build.
Needs a decisive 1-page PRD in docs/prds/ (per docs/prds/RULES.md) that settles where news lives, how a release page is derived, and how the two-component split (archied vs archie-agent) is presented.
Notes
CORRECTION (Sam, directly): pi.dev is a reference for the IDEA ONLY -- a news page and per-version release notes. It is explicitly NOT a design to clone: do not copy its visual design, copy/voice, URL scheme (/news/releases/0.87.0), section names or page structure. Build it as archie's own, on the existing MkDocs Material theme and archie's two-component release model (archied/vX.Y.Z + archie/vX.Y.Z from CHANGELOG.archied.md / CHANGELOG.archie.md).
DECISION (host): news + releases render in the existing MkDocs docs site at docs.offloaded.dev/news/. Astro/catlow-tech rejected as host (undeployed, no remote/CI, not in Ansible inventory, whole site login-gated = opposite access model). Part B therefore = MkDocs adapter + mkdocs.yml not_in_nav for news/archied/* + news/archie/*, in the SAME commit. Part A (docs/data/generated/releases.json from CHANGELOG headings, tools/newsgen, task news/news:check, release.sh --tag staging) approved as landed; keep it host-agnostic.
Close reason
done
Imported from beads archie-core-2ncm.2 · GitHub #1042 · type task · priority P1 · created 2026-09-21 · closed 2026-09-28
Lane B (archie-core). Add public news + releases in the style of pi.dev.
Reference: https://pi.dev/news (dated index) and https://pi.dev/news/releases/0.87.0 (per-version page: New Features / Fixes).
Must be generated, not hand-maintained per release: release history already exists in CHANGELOG.archied.md and CHANGELOG.archie.md, produced by tools/release.sh from conventional commits; tags are archied/vX.Y.Z and archie/vX.Y.Z. mkdocs.yml holds back archive/, inspiration/, prds/*, github-token.md; everything else under docs/ is public. `task docs:site` is mkdocs build --strict, so a dead internal link fails the build.
Needs a decisive 1-page PRD in docs/prds/ (per docs/prds/RULES.md) that settles where news lives, how a release page is derived, and how the two-component split (archied vs archie-agent) is presented.
### Notes
CORRECTION (Sam, directly): pi.dev is a reference for the IDEA ONLY -- a news page and per-version release notes. It is explicitly NOT a design to clone: do not copy its visual design, copy/voice, URL scheme (/news/releases/0.87.0), section names or page structure. Build it as archie's own, on the existing MkDocs Material theme and archie's two-component release model (archied/vX.Y.Z + archie/vX.Y.Z from CHANGELOG.archied.md / CHANGELOG.archie.md).
DECISION (host): news + releases render in the existing MkDocs docs site at docs.offloaded.dev/news/. Astro/catlow-tech rejected as host (undeployed, no remote/CI, not in Ansible inventory, whole site login-gated = opposite access model). Part B therefore = MkDocs adapter + mkdocs.yml not_in_nav for news/archied/* + news/archie/*, in the SAME commit. Part A (docs/data/generated/releases.json from CHANGELOG headings, tools/newsgen, task news/news:check, release.sh --tag staging) approved as landed; keep it host-agnostic.
### Close reason
done
---
_Imported from beads `archie-core-2ncm.2` · GitHub #1042 · type task · priority P1 · created 2026-09-21 · closed 2026-09-28_
sam
added the hightask labels 2026-10-27 13:34:43 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Lane B (archie-core). Add public news + releases in the style of pi.dev.
Reference: https://pi.dev/news (dated index) and https://pi.dev/news/releases/0.87.0 (per-version page: New Features / Fixes).
Must be generated, not hand-maintained per release: release history already exists in CHANGELOG.archied.md and CHANGELOG.archie.md, produced by tools/release.sh from conventional commits; tags are archied/vX.Y.Z and archie/vX.Y.Z. mkdocs.yml holds back archive/, inspiration/, prds/*, github-token.md; everything else under docs/ is public.
task docs:siteis mkdocs build --strict, so a dead internal link fails the build.Needs a decisive 1-page PRD in docs/prds/ (per docs/prds/RULES.md) that settles where news lives, how a release page is derived, and how the two-component split (archied vs archie-agent) is presented.
Notes
CORRECTION (Sam, directly): pi.dev is a reference for the IDEA ONLY -- a news page and per-version release notes. It is explicitly NOT a design to clone: do not copy its visual design, copy/voice, URL scheme (/news/releases/0.87.0), section names or page structure. Build it as archie's own, on the existing MkDocs Material theme and archie's two-component release model (archied/vX.Y.Z + archie/vX.Y.Z from CHANGELOG.archied.md / CHANGELOG.archie.md).
DECISION (host): news + releases render in the existing MkDocs docs site at docs.offloaded.dev/news/. Astro/catlow-tech rejected as host (undeployed, no remote/CI, not in Ansible inventory, whole site login-gated = opposite access model). Part B therefore = MkDocs adapter + mkdocs.yml not_in_nav for news/archied/* + news/archie/*, in the SAME commit. Part A (docs/data/generated/releases.json from CHANGELOG headings, tools/newsgen, task news/news:check, release.sh --tag staging) approved as landed; keep it host-agnostic.
Close reason
done
Imported from beads
archie-core-2ncm.2· GitHub #1042 · type task · priority P1 · created 2026-09-21 · closed 2026-09-28