---
title: "Feedback Examples"
description: "Patterns for page-level feedback, docs triage, and improvement loops."
canonical_url: "https://docs.bulkheados.com/content/feedback/"
template: "page-node"
schema_type: "WebPage"
---

<div class="docs-content">
<p class="docs-lead">The cleanest feedback widgets are lightweight. Ask one clear question, capture the answer quickly, and turn it into editorial work instead of analytics theatre.</p>

<h2 id="page-end-feedback">Page-End Feedback</h2>
<p>Mint includes a page-end prompt so every article can answer the same question: did this page help? Keep the interaction binary unless you have a staffed process for longer free-form submissions.</p>

<pre><code class="language-json">{
  "page": "/content/code-blocks",
  "response": "yes",
  "recorded_at": "2026-04-07T10:15:00.000Z",
  "source": "page-feedback"
}</code></pre>

<h2 id="triage-pattern">Triage Pattern</h2>
<p>A simple editorial loop works well:</p>
<ol>
<li>Watch for pages with repeated <strong>Needs work</strong> signals</li>
<li>Open the article and inspect whether it lacks examples, screenshots, or a concrete request/response</li>
<li>Patch the docs, then re-check the signal after the update ships</li>
</ol>

<h2 id="feedback-copy-example">Recommended Copy</h2>
<p>Shorter copy usually wins. These labels are enough:</p>
<ul>
<li><strong>Question:</strong> Was this page useful?</li>
<li><strong>Positive action:</strong> Yes, useful</li>
<li><strong>Negative action:</strong> Needs work</li>
</ul>

<div class="docs-callout docs-callout--warning">
<p><strong>Avoid this trap:</strong> Do not ask for detailed feedback on every page unless someone is actively reviewing it. Fast signals beat abandoned forms.</p>
</div>

<h2 id="what-to-improve-first">What To Improve First</h2>
<div class="docs-example-grid">
  <a class="docs-example-card" href="/content/code-blocks">
    <span class="docs-example-card__eyebrow">Usually Missing</span>
    <strong class="docs-example-card__title">Concrete snippets</strong>
    <span class="docs-example-card__body">If readers say a page is weak, it often needs one executable example, not more explanation.</span>
  </a>
  <a class="docs-example-card" href="/federation/comments">
    <span class="docs-example-card__eyebrow">Second Pass</span>
    <strong class="docs-example-card__title">Real-world workflows</strong>
    <span class="docs-example-card__body">Show what happens after publishing, searching, or receiving feedback, not just the initial setup step.</span>
  </a>
</div>
</div>