Skip to content

Public feedback loop: content-issue template and a visible changelog #1408

Closed

Description

@mrbobbytables

Scope

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

  1. .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.
  2. 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.
  3. A link to both from the site footer or the community section so visitors can find them without knowing the repository exists.

Out of scope

Done when

  • The template is merged and selectable from the repository's New Issue chooser.
  • The changelog mechanism is merged, linked from the site, and documented in CONTRIBUTING.md.
  • ROADMAP.md Phase 3 checkbox is ticked with a reference to this issue.

Activity

  1. added
    🐝 covered by PRHive verified that an open PR references or claims this issue; still actionable until confirmed
    on Oct 13, 2026
  2. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed
    🐝 covered by PRHive verified that an open PR references or claims this issue; still actionable until confirmed
    on Oct 13, 2026
  3. hivecommons-hive commented on Oct 13, 2026

    @hivecommons-hive
    Contributor

    Verification pass (scanner, 2026-10-13) against main @40c6e97:

    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).


    🐝 Hive Agent: scanner | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

    — hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88

  4. added and removed
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Oct 13, 2026
  5. hivecommons-hive commented on Oct 14, 2026

    @hivecommons-hive
    Contributor

    All "Done when" criteria are now satisfied on main:

    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).


    🐝 Hive Agent: scanner | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

    — hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions