If you've ever built a WordPress site for a client, you know the drill.
You spend weeks building something you're proud of. The site looks great, the pages are polished, Elementor did its thing. Then comes the review phase.
And suddenly your phone is on fire. WhatsApp messages with blurry screenshots. Emails with feedback like "the thing on the left, make it bigger." A Slack thread that spiraled into 47 messages about a single button color. A Zoom call that could have been a one-line comment. A Jira ticket that references a Google Doc that references another email that nobody can find anymore.
Sound familiar?
The breaking point
I was building a content-heavy site for a client — multiple pages, complex Elementor layouts, custom post types. The client needed to review everything before launch.
We tried everything. Shared staging links. Loom videos. Screenshot annotations. Google Docs with comments. Nothing stuck. The client would forget which version they were looking at, feedback would get lost, and I'd end up on a call re-explaining changes I'd already made twice.
I looked at tools like Marker.io, Atarim, and BugHerd. They're good products — but they're all external SaaS subscriptions starting at $49/month, they require clients to create accounts or install browser extensions, and they add another external dependency to every project.
I didn't want another tool my client had to learn. I wanted something that lived inside WordPress, felt native, and worked the way developers think.
The GitHub moment
Then it hit me.
GitHub pull requests already solved this problem for code. Inline comments anchored to specific lines, an approve/request changes flow, clear status tracking, threaded discussions. Developers use this workflow every single day and it just works.
What if content review in WordPress worked exactly like a GitHub PR?
So I built it.
What I built
Flow is a free WordPress plugin that brings a GitHub-style review and approval workflow natively into WordPress.
Here's how it works:
- You assign a reviewer to a post or page
- The reviewer opens a dedicated review page — they see the rendered content exactly as visitors will, not the editor
- They leave inline comments anchored directly to the content They approve or request changes
- You publish with confidence once approved
No SaaS subscription. No external service. No client logins — guests can review via a magic link without ever touching the WordPress admin.
It works with Gutenberg, Elementor, Classic Editor, and Bricks Builder out of the box.
The technical decisions worth mentioning
Why WordPress-native?
Every other tool in this space is a script tag wearing a plugin badge. They install a widget on your site that phones home to an external server. Flow runs entirely inside WordPress using native APIs and WordPress UI libraries. No external dependency, no data leaving your server.
Why inline comments instead of screenshots?
Screenshot annotation tools like Marker.io are great for bug reporting. But for content review — where a client needs to say "change this paragraph" or "this heading doesn't work" — inline comments anchored to the actual content block are faster and more precise. The reviewer clicks directly on what they mean.
Why the GitHub PR model?
Developers already understand it intuitively. When I showed early users the approve/request changes flow, nobody needed a tutorial. The mental model transferred immediately.
Try it
Flow is free on WordPress.org:
http://wordpress.org/plugins/jumplinks-editorial-workflow
If you've ever suffered through client feedback chaos on a WordPress project — I built this for you. Would love to hear how your review process works currently and what you'd want from a tool like this.
Top comments (0)