Client feedback and editorial workflow with inline comments and a familiar WordPress style review experience.

Abiodun Adeniji

Content Flow Manager

A professional editorial content approval workflow for WordPress. Perfect for multi-author sites.

JumpLinks Systems

alincozari

<p>Frustrated with client feedback chaos, multiple staging environments, endless meetings that could have been an email, hundreds of Jira tickets and lost Slack discussions?</p>
<p>Jumplinks Flow was inspired by the GitHub pull request review experience with inline comments and approval or change requests workflow that developers love, brought natively into WordPress for content and site reviews. No SaaS subscription, no external tools, just a familiar, focused review experience your team will pick up from day one.</p>
<p>If your current process depends on long comment threads, scattered docs and email, or third-party review tools, Flow gives you a cleaner path without complex setup or heavyweight workflow tools.</p>
<h4>⚙️ How it works</h4>
<ol>
<li>You assign a reviewer to the content.</li>
<li>The reviewer opens the review page and sends feedback via inline comments anchored to the content.</li>
<li>The reviewer requests changes or approves.</li>
<li>If changes are requested, repeat 2–3 until approval is received.</li>
<li>You publish with confidence once the content is approved.</li>
</ol>
<h4>🎯 Best for</h4>
<ul>
<li>Agencies and developers who present in-progress work to clients for feedback and signoff</li>
<li>Editorial teams that need a clear draft-to-publish workflow</li>
<li>Website owners that want structure without heavy workflow configuration</li>
</ul>
<h4>💡 Why teams choose Flow</h4>
<ul>
<li><strong>GitHub-style workflow:</strong> Leave feedback exactly where it matters via inline comments so edits are clearer and faster.</li>
<li><strong>Review directly on rendered page:</strong> Reviewers don’t need access to the content editor; they review the rendered output.</li>
<li><strong>Works with any editor:</strong> Dedicated integration with Gutenberg, Classic Editor, Elementor, Bricks Builder, Beaver Builder, Divi, Avada, and Breakdance, but all editors are supported.</li>
<li><strong>Simple review and approval:</strong> Move content through practical statuses such as in review, changes requested, and approved.</li>
<li><strong>Familiar Gutenberg-style review page:</strong> Dedicated review UI that feels native to WordPress.</li>
<li><strong>Fast team onboarding:</strong> Minimal setup and intuitive UI for writers, editors, and reviewers.</li>
<li><strong>Status-change notifications:</strong> Keep everyone aligned with timely workflow updates.</li>
<li><strong>Lightweight by design:</strong> Built with native WordPress APIs and UI libraries.</li>
</ul>
<h4>🧩 Built for your content stack</h4>
<ul>
<li><strong>Editor support:</strong> Dedicated integration with Gutenberg, Classic Editor, Elementor, Bricks Builder, Beaver Builder, Divi, Avada, and Breakdance workflows.</li>
<li><strong>Content type flexibility:</strong> Use Flow for posts, pages, products, and custom post types.</li>
<li><strong>WooCommerce friendly:</strong> Works smoothly with WooCommerce-based editorial setups.</li>
</ul>
<h4>✨ What makes Flow different</h4>
<p>Most feedback tools are paid-only SaaS subscriptions that charge per reviewer and require clients to sign up for separate accounts. Flow runs entirely inside your WordPress site, and lets you invite reviewers with a single link — no signup, no monthly fee, no third-party service collecting your content.</p>
<p>Editorial workflow plugins optimize for maximum configuration. Flow optimizes for feedback momentum. You get a clear approval process and contextual collaboration without overwhelming your team or clients with complexity.</p>
<p>If you want an editorial workflow that is modern, focused, and easy to use from day one, Flow is built for you.</p>
<h3>🚀 Pro features</h3>
<p>Flow Pro extends the free workflow with the following additions:</p>
<h4>👥 Multiple reviewers</h4>
<p>Assign any number of reviewers per post and set a minimum approval count. Each vote (approved / changes requested / pending) is tracked independently.</p>
<h4>🔗 Open to public</h4>
<p>Add external email addresses to a post review or site review. Each recipient gets a signed magic link that drops them straight into the review with their identity bound to that link.</p>
<h4>🌐 Site-wide review</h4>
<p>Request a site review with one or many reviewers — logged-in users, external email invitees, or both. Reviewers land in a review mode overlaying your site, can navigate freely, and leave anchored comments on any page.</p>
<h4>💬 Improved comments</h4>
<p>A TipTap-powered editor brings bold, italics, headings, lists, links, quotes, and code blocks to every review comment. Type <code>@</code> to mention any reviewer, the author, or external invitees.</p>
<h4>🔔 Slack integration</h4>
<p>Connect a Slack bot once and Flow DMs reviewers when they’re assigned, mentioned, approved, asked for changes, or invited to a site review. Member IDs auto-resolve by email; users can override per-event opt-ins from their profile.</p>
<h4>📱 Device selector</h4>
<p>A device switcher in the review bar lets reviewers toggle between desktop, tablet, and mobile widths without leaving the page.</p>
<h4>📊 Activity tracking</h4>
<p>An activity bar on the review page tracks every status change — pending review, in review, changes requested — along with the user who triggered each event.</p>
<h3>Development</h3>
<h4>Where is the JavaScript and CSS source?</h4>
<p>Human-editable source for the compiled assets in <code>build/</code> lives in the <code>src/</code> directory. Files under <code>build/</code> are generated by webpack; edit <code>src/</code> instead of hand-editing <code>build/</code>.</p>
<h4>How do I rebuild the compiled assets?</h4>
<p>From the plugin directory, with a supported Node.js release:</p>
<ol>
<li>Run <code>npm install</code> or <code>npm ci</code> to install dependencies.</li>
<li>Run <code>npm run build</code> to regenerate webpack output.</li>
</ol>
<h4>Third-party JavaScript</h4>
<p>Packages such as <code>@wordpress/scripts</code> and <code>@wordpress/icons</code> are declared in <code>package.json</code>. After <code>npm install</code>, see each package under <code>node_modules/</code> for license text, or refer to the upstream WordPress repositories.</p>
<h3>External services</h3>
<p>This plugin loads avatar images from Gravatar (operated by Automattic), which is a third-party service.</p>
<ul>
<li><strong>What is sent:</strong> an MD5 hash of the user’s email address, generated by WordPress core via <code>get_avatar_url()</code>. No raw email address leaves the site.</li>
<li><strong>When:</strong> whenever the plugin renders a comment author avatar (review page comment cards, inline comment threads) or a reviewer/requester avatar (REST responses for the review sidebar and the Elementor, Bricks, Beaver Builder, Divi, Avada, and Breakdance drawers).</li>
<li><strong>Why:</strong> to display each commenter’s avatar next to their comment, matching the rest of the WordPress avatar experience.</li>
<li><strong>Service URL:</strong> https://gravatar.com/</li>
<li><strong>Terms:</strong> https://automattic.com/terms/</li>
<li><strong>Privacy:</strong> https://automattic.com/privacy/</li>
</ul>
<p>This is the same Gravatar integration that ships with WordPress core; the plugin does not contact any other external services.</p>


Jumplinks Flow – Editorial Feedback, Review & Approval Workflow


I didn't know we'd ever have this in WordPress, it’s like being in Figma, but better because it's a live environment! What I've tested till now:




Clear on-site feedback chat: You can easily select specific text and images on a page to leave comments, replies, resolving etc. The thing I like most is that I have the ability to see the chat history and also request edits even after final approval.



Taking WP user roles to the next level: It's the ideal balance between an editor's freedom and a contributor's limitations. Content can only go live after a reviewer grants final approval.



Clean UI: The interface feels completely native to WordPress, free of any bloated overdesign.




I can't wait to test this on a WooCommerce webshop next.


Alternatives to Jumplinks Flow – Editorial Feedback, Review & Approval Workflow

Top alternatives