Skip to content

Name GitHub issues on the specification repository as the comment channel - #44

Draft
cbyrd01 wants to merge 1 commit into
mainfrom
docs/comment-channel
Draft

cbyrd01 wants to merge 1 commit into
mainfrom
docs/comment-channel

Conversation

@cbyrd01

@cbyrd01 cbyrd01 commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Merge on flip day, not before. The specification repository is private until then, and the site must never send readers to a repository they cannot open.

Closes #43

Names the comment channel Chris approved: GitHub issues on the specification repository.

Changes

  • New Feedback component. It holds the sentence "The draft is open for review. To comment on it, open an issue in the specification repository on GitHub." The link goes to the repository's new-issue page, which is GITHUB.specsNewIssue in site.config.ts.
  • Home page. The closing note under the reader groups uses the component. The old note was a plain-text constant with a comment saying the channel was undecided. Both are gone, and the note keeps its muted style.
  • Introduction, "Reviewing the draft". The section uses the component and then adds "The draft and its companion documents are in the same repository."
  • Other mentions. No other page repeats the old "A channel for comments has not been chosen yet" line. /llms.txt does not mention comments, so it is unchanged.

The repository has issues enabled and no issue templates, so the link opens a blank new issue. Templates in the specification repository would be a separate change, made there.

Checks

  • astro check: 0 errors, 0 warnings, 0 hints.
  • astro build and check-site.mjs: 19 pages checked, 0 errors.
  • git merge-tree against origin/main: clean. If main moves before flip day, re-check before merging.
  • Both changed sections were checked in a headless browser at desktop width.

Posted by Claude (AI assistant) on behalf of Christopher Byrd

🤖 Generated with Claude Code

https://claude.ai/code/session_012CEyiXRPrNfjwX3iEx99dw

…nnel

The home page's closing note and the Introduction's "Reviewing the
draft" section said a channel for comments had not been chosen. Both
now say to open an issue in the specification repository on GitHub,
from one Feedback component, so the channel is named in one place.
GITHUB.specsNewIssue holds the link.

Merge on flip day: the specification repository is private until then.

Closes #43

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CEyiXRPrNfjwX3iEx99dw
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Name GitHub issues on the specification repository as the comment channel

1 participant