Skip to content

Inline feedback — let readers comment on the page #3

@kobzevvv

Description

@kobzevvv

Problem

You send a design mockup, a report draft, or a proposal to a client. They reply via email: "Looks good, but change the thing on page 2." Which thing? What page 2? Now you're on a call clarifying what they meant.

Feedback lives in one place (email, Slack), the document lives in another (a link). Context is lost in translation.

Solution

Add an optional feedback bar to published pages. Readers can leave short messages directly on the page — no account needed.

npx instant-publish deploy design-v2.html --slug landing-redesign --feedback
# Published: https://chillai.space/p/landing-redesign (feedback enabled)

A minimal floating bar appears at the bottom of the page:

┌─────────────────────────────────────────────────┐
│  💬  Leave feedback for the author              │
│  [Your message...                    ] [Send]   │
└─────────────────────────────────────────────────┘

The author gets notified (webhook, email, or CLI).

Why this is powerful

Think about the old design review workflow:

  1. Designer exports PDF, emails it
  2. Client opens PDF, screenshots a section, annotates it, emails back
  3. Designer asks for clarification
  4. Three days of back-and-forth

Now imagine:

  1. Designer publishes HTML: npx instant-publish deploy mockup.html --feedback
  2. Client opens the link, types "Love the header, but the CTA button should be green" directly on the page
  3. Designer gets the message instantly, updates the page
  4. Done. Minutes instead of days.

Use cases

  • Design reviews — clients comment directly on the deliverable
  • Report drafts — stakeholders flag issues before the final version
  • Documentation — readers report errors or ask questions
  • Proposals — prospects ask clarifying questions without switching to email

Implementation ideas

  • Feedback stored in KV: feedback:{slug}:{timestamp}{ message, created }
  • Injected as a small JS widget at the bottom of the page (author opts in with --feedback)
  • No auth for readers — low friction is key
  • Author retrieves feedback: npx instant-publish feedback <slug>
  • Optional webhook URL for real-time notifications
  • Rate limiting to prevent spam (IP-based, 5 messages per hour)

UX principles

  • Zero friction for the reader: no signup, no login, just type and send
  • Minimal UI: doesn't distract from the content
  • Author controls: can disable feedback, delete messages, or add a webhook

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions