/ feedback pins that stay on the right element
acme.github.io/handbook/docs/intro/1024px

Docs · Introduction

Ship feedback straight from the page

Reviewers pin comments to the parts of a Pages site they care about. Every thread lives in GitHub Discussions, next to the code.

Getting started

Add the script to your deploy step. The reusable workflow does this for you, and turns on Discussions for the repo.

npx pages-feedback init
  1. Sign in with your GitHub account.
  2. Press C, then click anything on the page.
  3. Copy open threads for a coding agent.

What you get

  • Pins Comments stay attached to the element, not the pixel.
  • Search Find any page in under 50ms.
  • Deploy previews Review every branch before it ships.

press c, then click anything · drag the bubble to any edge · squeeze the width to fold the nav

preview the agent prompt (5 open threads)
# Feedback to address: /docs/intro/ (build a1b2c3d)

## 1. [Feedback] Open · https://github.com/acme/handbook/discussions/41
**HTML id:** `#setup`
**Element:** `main > section:nth-of-type(2) > h2#setup`
**Text:** "Getting started"
**Source hint:** search the repo for `id="setup"` or the text above
**Note:** this element wasn't found on the current build. It may have been removed or rewritten.
**Thread:**
- @alice: This heading is too close to the hero on mobile.
- @bob: Agree, 16px more spacing would fix it.

## 2. [Positive] Open · https://github.com/acme/handbook/discussions/42
**HTML id:** `[data-feedback-id="hero-cta"]`
**Element:** `main > section:nth-of-type(1) > div > a[data-feedback-id="hero-cta"]`
**Text:** "Get started"
**Source hint:** search the repo for `data-feedback-id="hero-cta"` or the text above
**Note:** this element wasn't found on the current build. It may have been removed or rewritten.
**Thread:**
- @sam: Love that the primary action is obvious now.

## 3. [Question] Open · https://github.com/acme/handbook/discussions/43
**HTML id:** none on this element
**Element:** `main > section:nth-of-type(2) > aside`
**Text:** "Heads up: device codes expire after 15 minutes."
**Source hint:** search the repo for the text above
**Note:** this element wasn't found on the current build. It may have been removed or rewritten.
**Thread:**
- @mei: Is it 15 minutes on Enterprise too? I thought it was configurable.

## 4. [Feedback] Open · https://github.com/acme/handbook/discussions/44
**HTML id:** none on this element
**Element:** `main > section:nth-of-type(3) > ul > li:nth-of-type(2)`
**Text:** "Search Find any page in under 50ms."
**Source hint:** search the repo for the text above
**Note:** this element wasn't found on the current build. It may have been removed or rewritten.
**Note:** written against build 9f3e1a0.
**Thread:**
- @alice: The search icon looks blurry on retina screens.

## 6. [Feedback] Open · https://github.com/acme/handbook/discussions/46
**HTML id:** none on this element
**Element:** `main > section:nth-of-type(2) > pre`
**Text:** "npx pages-feedback init"
**Source hint:** search the repo for the text above
**Note:** this element wasn't found on the current build. It may have been removed or rewritten.
**Thread:**
- @sam: This command should copy with one click.

## Instructions
Make the minimal change to resolve each thread. Reply with a summary per thread number.