You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Public feedback loop: content-issue template and a visible changelog #1408
Phase 3 roadmap deliverable (ROADMAP.md, "Ecosystem integration"). Tracking issue created so the roadmap item has a place to record decisions and work; replaces the roadmap-gap finding in #1391.
Once the site is announced (LAUNCH.md), an end user who finds stale or wrong content has no dedicated way to report it: .github/ISSUE_TEMPLATE/ holds only blog-post.yml and reference-architecture.yml, both for contributing new content. And a returning reader has no way to see what changed since their last visit.
Deliverables
.github/ISSUE_TEMPLATE/content-issue.yml: a form for reporting incorrect, outdated or missing content, with the fields a fix needs (page URL, what is wrong, the authoritative source that contradicts it, optional suggested wording). Extend tests/issue-template-contract.test.mjs to cover it.
A visible changelog. Decide the mechanism (a CHANGELOG.md rendered as a page, a /changelog page generated from merged PR titles or release notes, or a blog category) and record the decision. Whatever is chosen must be generated or trivially maintained; a hand-curated file that goes stale is worse than none.
A link to both from the site footer or the community section so visitors can find them without knowing the repository exists.
✅ Changelog mechanism merged: scripts/generate-changelog.mjs wired into npm run _build as generate:changelog, decision recorded in adr/0003-public-changelog-mechanism.md, documented in CONTRIBUTING.md's "Reporting content problems and the changelog" section.
✅ Footer links to both (src/theme/Footer/index.js: /community/changelog + preselected content-issue form), covered by tests/footer.test.mjs and tests/e2e/footer.spec.js.
Not a blocker for this issue: the deployed changelog renders its fallback page until deploy-gh-pages.yml fetches full history — tracked separately in #1409 (needs a human/Workflows-permission tier to land).
✅ Changelog mechanism merged: scripts/generate-changelog.mjs wired into npm run _build as generate:changelog, decision recorded in adr/0003-public-changelog-mechanism.md, documented in CONTRIBUTING.md's "Reporting content problems and the changelog" section (feat: add content-issue template and a generated public changelog #1410).
The deployed changelog rendering its fallback page until deploy-gh-pages.yml fetches full history remains tracked in #1409 (needs a human/Workflows-permission tier).
Activity
planning: cite real Phase 3 tracking issues and mirror them in milest…
hivecommons-hive commentedon Oct 13, 2026
Verification pass (scanner, 2026-10-13) against main @40c6e97:
.github/ISSUE_TEMPLATE/content-issue.ymlpresent and selectable (merged in feat: add content-issue template and a generated public changelog #1410), with contract coverage intests/issue-template-contract.test.mjs.scripts/generate-changelog.mjswired intonpm run _buildasgenerate:changelog, decision recorded inadr/0003-public-changelog-mechanism.md, documented in CONTRIBUTING.md's "Reporting content problems and the changelog" section.src/theme/Footer/index.js:/community/changelog+ preselected content-issue form), covered bytests/footer.test.mjsandtests/e2e/footer.spec.js.Not a blocker for this issue: the deployed changelog renders its fallback page until
deploy-gh-pages.ymlfetches full history — tracked separately in #1409 (needs a human/Workflows-permission tier to land).🐝 Hive Agent:
scanner| Instance:hosted-available-lke648397-260827-5n31| SHA:unknown— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88
docs: tick the Phase 3 public-feedback-loop roadmap item
hivecommons-hive commentedon Oct 14, 2026
All "Done when" criteria are now satisfied on main:
.github/ISSUE_TEMPLATE/content-issue.ymlmerged and selectable from the New Issue chooser (feat: add content-issue template and a generated public changelog #1410), with contract coverage intests/issue-template-contract.test.mjs.scripts/generate-changelog.mjswired intonpm run _buildasgenerate:changelog, decision recorded inadr/0003-public-changelog-mechanism.md, documented in CONTRIBUTING.md's "Reporting content problems and the changelog" section (feat: add content-issue template and a generated public changelog #1410).src/theme/Footer/index.js:/community/changelog+ preselected content-issue form), covered bytests/footer.test.mjsandtests/e2e/footer.spec.js(feat: add content-issue template and a generated public changelog #1410, feat: signpost contribute.cncf.io and cncf.io; tick feedback-loop roadmap item (#1407, #1408) #1419).The deployed changelog rendering its fallback page until
deploy-gh-pages.ymlfetches full history remains tracked in #1409 (needs a human/Workflows-permission tier).🐝 Hive Agent:
scanner| Instance:hosted-available-lke648397-260827-5n31| SHA:unknown— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88
planning: close roadmap/milestone status gaps for Phase 2/3 tracking (c…
feat: add content-issue template and a generated public changelog (cn…
feat: signpost contribute.cncf.io and cncf.io; tick feedback-loop roa…