George Stephanis

<p>Tuft adds a floating button to every page on your site. When clicked, it enters a targeting mode that lets the visitor click any element on the page to annotate it. The plugin captures the DOM selector, click coordinates, viewport dimensions, form field state, and an in-browser screenshot, then presents a drawing toolbar so the reviewer can mark up the screenshot before typing their feedback. Everything is stored locally as a custom post type for admin review.</p>
<h4>Key features</h4>
<ul>
<li><strong>Click-to-annotate</strong> — click the “Feedback” button then click any element. The hovered element highlights so you know exactly what you’re selecting.</li>
<li><strong>In-browser screenshots</strong> — uses html2canvas (bundled with the plugin, no CDN dependency) to capture the visible viewport at the moment of submission.</li>
<li><strong>Freehand canvas annotation</strong> — a drawing toolbar below the screenshot preview lets reviewers draw freehand strokes or rectangles, undo the last stroke, or clear all marks. Annotations are baked into the submitted JPEG on the client.</li>
<li><strong>Context capture</strong> — records the CSS selector, viewport-relative click coordinates, viewport dimensions, and any visible form field values (passwords excluded).</li>
<li><strong>Feedback modal</strong> — clean overlay collects the visitor’s feedback text alongside the annotated screenshot. Logged-in users are not prompted for name or email — their WordPress account details are used automatically. Guest visitors see name and email fields.</li>
<li><strong>Widget visibility controls</strong> — choose who sees the feedback button: everyone (including logged-out visitors), logged-in users only, editors and above, or administrators only. Configured under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Tuft Feedback</strong>.</li>
<li><strong>Submission rate limiting</strong> — cap submissions per IP address per hour to protect against spam. Set to 0 to disable. Tracked via post meta queries.</li>
<li><strong>Built-in notifications</strong> — email a comma-separated list of addresses and/or POST a JSON payload to any number of webhook URLs on every submission. Works with Slack incoming webhooks, Discord, Teams, Zapier, Make, and any HTTP endpoint.</li>
<li><strong>Local storage</strong> — submissions saved as a <code>tuft_feedback</code> custom post type with full metadata and a screenshot attachment.</li>
<li><strong>Admin review</strong> — list table with columns for feedback text, source page, element selector, submitter, and screenshot thumbnail. Full detail view with screenshot in the post editor.</li>
<li><strong>Alpaca Issue Tracker integration</strong> — if <a href="https://wordpress.org/plugins/alpaca-issue-tracker/" rel="ugc">Alpaca Issue Tracker</a> is installed, each submission is automatically mirrored as a Kanban issue on the Alpaca board. The Tuft admin menu moves under the Alpaca Project Board menu.</li>
</ul>
<h4>Intended use</h4>
<p>This plugin is designed for <strong>local development and staging environments</strong> where you want clients or team members to leave visual design notes without logging in to a project management tool. The widget visibility setting under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Tuft Feedback</strong> controls who sees the button; the REST endpoint that receives submissions is open by default — review the security notes before deploying to a publicly accessible production site.</p>
<h4>Alpaca Issue Tracker integration</h4>
<p>When <a href="https://wordpress.org/plugins/alpaca-issue-tracker/" rel="ugc">Alpaca Issue Tracker</a> is active alongside Tuft:</p>
<ul>
<li>Each submission creates a matching <code>alpaca_issue</code> in your board’s default (lowest-score) column.</li>
<li>Issues are tagged with the submitter’s browser and the type “Tuft” for easy filtering.</li>
<li>The Tuft admin menu moves under the <strong>Project Board</strong> submenu, so the Alpaca board becomes the primary triage interface.</li>
<li>Click any row in the Tuft list to open the full detail view including the annotated screenshot.</li>
</ul>


Tuft Feedback

Collect visual design feedback directly on the page — visitors click any element, annotate a screenshot, and add a note without leaving the browser.

Mehul Gohil

<p>PreviewShare is a secure public preview plugin for WordPress. It helps editors share draft posts, pending pages, scheduled content, private posts, and other enabled public post types through controlled preview links without publishing early or creating temporary reviewer accounts.</p>
<p>Use PreviewShare when a client, legal reviewer, teammate, editor, or stakeholder needs to review WordPress content before it goes live. Each preview URL uses a random token, can expire automatically, can be revoked, and is designed for private review workflows such as client approval, content approval, editorial review, and scheduled campaign checks.</p>
<p>PreviewShare stores token hashes instead of plain-text tokens, adds noindex/nofollow robots directives to shared previews, and shows a clear preview banner on private preview pages.</p>
<h4>Common use cases</h4>
<ul>
<li>Share a WordPress draft post with a client before publishing.</li>
<li>Send a private preview link for a pending page, scheduled campaign, or unpublished landing page.</li>
<li>Let stakeholders review content without giving them a WordPress login.</li>
<li>Create separate labeled preview links for legal review, client review, editorial review, or team approval.</li>
<li>Revoke access after feedback is complete or when a preview link should no longer work.</li>
<li>Keep search engines from indexing private preview URLs with robots directives.</li>
</ul>
<h4>Key features</h4>
<ul>
<li>Generate secure public preview links from the block editor, Classic Editor, post list table, or Preview dropdown.</li>
<li>Share pretty URLs such as <code>https://example.com/preview/exampletoken</code>.</li>
<li>Set a default expiration time for preview links from the PreviewShare settings screen.</li>
<li>Override the expiration time per post or page.</li>
<li>Create multiple labeled preview links for different reviewers.</li>
<li>Revoke preview access when a link should stop working.</li>
<li>View and manage preview link status, expiry, labels, and view counts from the settings screen.</li>
<li>Choose which public post types support public preview sharing.</li>
<li>Keep token lookup fast with optional object cache support.</li>
</ul>
<h4>How PreviewShare protects preview links</h4>
<p>PreviewShare is built for private review, not public publishing. It uses random preview tokens, stores token hashes in WordPress post meta, supports automatic expiration, supports manual revocation, and sends <code>noindex</code>, <code>nofollow</code>, <code>noarchive</code>, <code>nosnippet</code>, and <code>noimageindex</code> directives for preview requests.</p>
<p>Anyone with a valid preview URL can open that preview, so links should still be shared only with intended reviewers.</p>
<h3>Development</h3>
<p>The public source repository is available at https://github.com/mehul0810/previewshare.</p>
<p>Production ZIP files are built from the source repository with:</p>
<pre><code>npm install
npm run plugin-zip
</code></pre>
<p>The release artifact includes compiled assets, Composer autoload files, <code>composer.json</code>, plugin PHP, languages, readme, and license files. Development files such as <code>node_modules</code>, source assets, CI configuration, tests, and build tooling are excluded from production ZIP files.</p>


PreviewShare

Create secure public preview links for WordPress drafts, scheduled posts, and client reviews without user accounts.

Tuft Feedback vs PreviewShare