Pane Studio

<p><strong>Breadbugger</strong> is a bug tracking tool built for the pre-launch phase of a WordPress site — the moment when designers, QA, developers and clients walk through the site looking for issues before go-live.</p>
<p>Three complementary surfaces:</p>
<ol>
<li><strong>On-page floating widget</strong> — open the widget with a configurable keyboard shortcut, “pin” reports directly to the HTML element they refer to, attach screenshots captured on-the-fly from the browser.</li>
<li><strong>Clean admin list</strong> — manage every report from a compact full-screen view: filter by status, priority, author; sort manually with drag & drop; reply with inline notes.</li>
<li><strong>REST API for external clients</strong> — app-password gated endpoints to integrate your bug tracker with CLIs, AI coding assistants, or custom scripts.</li>
</ol>
<h4>Key features</h4>
<ul>
<li><strong>Stable pin selectors</strong> — element selector built via a cascade: <code>data-breadbugger-name</code> (opt-in dev), then stable <code>id</code>, then semantic class, then positional CSS. Pins survive refactors.</li>
<li><strong>Configurable hotkey</strong> — press the keys to set your preferred combo, with browser/OS collision validation.</li>
<li><strong>Reporter / manager role model</strong> — assign who can open reports (reporter) and who can manage them all (manager) via custom capabilities on any WordPress role.</li>
<li><strong>Author filter + configurable visibility</strong> — managers can see and filter by author; reporters can optionally see only their own bugs.</li>
<li><strong>In-browser screenshots</strong> — automatic capture via <code>getDisplayMedia</code> (HTML2Canvas-Pro as a fallback for modern CSS like <code>oklch</code> / <code>color-mix</code>).</li>
<li><strong>Internationalized</strong> — Italian source, .po / .mo translations, .pot template ready for any language.</li>
<li><strong>Built-in feedback channel</strong> — settings form to send bug reports / feature requests / questions to the author via <code>wp_mail</code>.</li>
<li><strong>Branded email notifications</strong> — HTML emails for @mentions in notes and (optional) for new bugs and resolved bugs, with per-recipient frequency: all events, accorpate (timeout-based), daily digest, weekly digest, or none.</li>
</ul>
<h4>Use case</h4>
<p>Client site pre-go-live: 5-10 people testing in parallel. Each one loads the site, opens the widget with a shortcut, pins the issue directly on the affected element. The PM / dev watches the admin list, sorts by priority, assigns fixes, marks resolved.</p>
<p>Standalone. No external SaaS required. No data sent to third-party servers. Your bugs stay in your database.</p>


Breadbugger

On-page bug tracker for pre-launch QA. Pin reports directly on the page, manage them in a clean admin list, integrate with external clients via REST.

nokazehayato

<p><strong>Stop forgetting to disable WP_DEBUG before client handoff.</strong><br />
Noshi-Kanamer’s pre-launch checklist catches the things that always slip through — WP_DEBUG, noindex, test content, unused media — before you hand off to a client.</p>
<p>Unlike file-collection portals, Noshi-Kanamer focuses on the engineering side of handoff — catching WP_DEBUG, noindex, debug.log, and other technical loose ends before delivery.</p>
<p>Noshi-Kanamer is a pre-launch checklist and cleanup toolkit for WordPress freelancers and agencies. It helps you prepare a WordPress site for client delivery — clean up test content, check launch settings, hide Gutenberg blocks the client doesn’t need, and keep their admin experience focused.</p>
<p>The Pre-Launch tab is your final checkpoint before delivery: delete test content, flush rewrite rules, check WP_DEBUG, and confirm search engine indexing — all without leaving the admin. When the checklist clears, your site is ready to hand off.</p>
<p>Noshi-Kanamer supports two halves of a client project: tools that help while you build — Hide Blocks, Block Showcase, Test Posts, Media Manager, and Site Check — and a final checklist that confirms everything is ready before you hand off: Pre-Launch.</p>
<h4>Block Showcase</h4>
<p>Instantly render every registered block on any page or post. Insert the Block Showcase block, click “Generate Showcase”, and all available blocks appear in one place — ready for client review or your own reference.</p>
<p>No more hunting through the block inserter to find what’s available.</p>
<h4>Hide Blocks</h4>
<p>Remove unwanted default blocks (social links, YouTube embed, etc.) from the editor with a single click. Applied globally across all users — not just per-user preferences.</p>
<p>When you’re ready to deliver, the Pre-Launch tab generates a <code>functions.php</code> snippet to make the setting permanent. Deactivate or remove the plugin without losing your configuration.</p>
<h4>Test Posts</h4>
<p>Generate flagged test posts in one click. Each post is marked internally, so you can delete all test content before launch with zero risk of touching real posts.</p>
<h4>WordPress Pre-Launch Checklist</h4>
<p>A checklist that actually does the work. Before handing off the site, the Pre-Launch tab handles everything in one screen:</p>
<ul>
<li><strong>Delete all test posts</strong> — removes every flagged test post instantly</li>
<li><strong>Move Block Showcase pages to trash</strong> — cleans up pages containing the Block Showcase block</li>
<li><strong>Flush rewrite rules</strong> — prevents 404 errors after migration to production</li>
<li><strong>Search engine indexing</strong> — detects if your site is still set to noindex, with a direct link to fix it</li>
<li><strong>Admin email address</strong> — shows the current email with a direct link to update it</li>
<li><strong>WP_DEBUG status</strong> — alerts if debug mode is still on, with a copy-paste fix</li>
<li><strong>File editor, XML-RPC, debug.log, and the default ‘admin’ username</strong> — checks four common security loose ends, each with a one-click fix or guidance to resolve it</li>
<li><strong>Persist block visibility</strong> — generates a <code>functions.php</code> snippet to keep your Hide Blocks settings after deactivating or removing the plugin</li>
</ul>
<p>When all tasks are complete, a <strong>“Ready to launch”</strong> banner confirms the site is clean and ready for handoff. A copyable summary report lets you document the cleanup for your client.</p>
<h4>Site Check</h4>
<p>Taking over an existing site? The Site Check tab scans every installed plugin (active and inactive) against WordPress.org and flags anything that hasn’t been updated in 6+ months or 1+ year — with results sorted so the plugins that need attention appear first. It’s the fastest way to spot outdated, possibly abandoned plugins before you start working on a client’s site.</p>
<h4>Media Manager</h4>
<p>Keep your media library clean while you build. The Media Manager tab (Tools > Noshi-Kanamer) scans every image in your library and flags the ones that aren’t referenced anywhere in your content, so clutter doesn’t quietly pile up over the course of a project.</p>
<p>Each image in the media library is scanned automatically:</p>
<ul>
<li><strong>“Unused” badge</strong> — appears on any image that isn’t used in post content, featured images, or custom fields (including ACF image and gallery fields)</li>
<li><strong>“Used In” field</strong> — open any media attachment to see exactly which posts or pages reference it</li>
<li><strong>Bulk delete</strong> — select unused images in the Media Manager tab and permanently delete them in one go — handy for a final sweep before client handoff, too</li>
</ul>
<h4>Built for WordPress Freelancers & Agencies</h4>
<p>WordPress freelancers and agencies who build sites for clients and want to eliminate the repetitive, error-prone steps before delivery.</p>
<p>If you’ve ever shipped a site with <code>WP_DEBUG</code> still on, noindex still set, or test posts still in the database — this plugin is for you.</p>
<p>Hundreds of downloads since launch — built by a working WordPress developer.</p>
<h3>Source Code</h3>
<p>The compiled JavaScript in the <code>build/</code> directory is generated from the JSX source files in <code>src/</code> using Vite. The full source code is included in the plugin package under <code>src/</code>.</p>


Noshi-Kanamer – WordPress Pre-Launch Checklist & Client Handoff Toolkit

WordPress pre-launch checklist and client handoff toolkit for freelancers and agencies. Delete test content, check WP_DEBUG, remove unused media.

Breadbugger vs Noshi-Kanamer – WordPress Pre-Launch Checklist & Client Handoff Toolkit