| 开发者 |
jumplinks
alincozari |
|---|---|
| 更新时间 | 2026年6月9日 14:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/jumplinks-editorial-workflow directory, or install the plugin through the WordPress plugins screen.Assign a reviewer, collect feedback via inline comments, request changes or approve, and publish when approved.
The actual page exactly as visitors will see it — Flow renders the content through your theme on the frontend. Inline comments anchor to the rendered output, so reviewers catch layout, spacing, and typography issues that the editor view hides. Reviewers also don't need to access the editor to leave feedback.
Flow is designed for Gutenberg, Classic Editor, Elementor, Bricks Builder, Beaver Builder, Divi, Avada, and Breakdance publishing workflows.
Flow ships with native integrations for Gutenberg, Classic Editor, Elementor, Bricks Builder, Beaver Builder, Divi, Avada, and Breakdance. If you work in a different editor, you can still use Flow — just open the post in Gutenberg or Classic Editor (both included with WordPress) to request reviews, manage reviewers, and track status. Your existing editor stays untouched for the actual content work.
Yes. You can enable the review workflow for posts, pages, products, and custom post types from the settings screen. We cannot guarantee compatibility with all custom content types, but we are confident most cases are handled.
Yes. Flow sends email notifications for key review lifecycle events, helping teams stay aligned on status changes. Slack integration is also included in the Pro version.
Yes. Flow is compatible with WooCommerce-powered sites and content workflows.
Flow is ideal for content and editorial teams that need a simple review and approval workflow in WordPress without the overhead of enterprise-style configuration. It also works well for freelance developers and agencies who want a structured way to share in-progress work with clients for feedback and approval, without sending screenshots or asking clients to navigate the WordPress admin.
Yes. Add the client as a user with a reviewer-eligible role, assign them as the reviewer, and send them the review page link. They land on a focused page with the page or post preview, leave inline comments anchored to specific content, and approve or request changes — without ever needing to learn the WordPress editor. In the PRO version you can even send the review link to an anonymous user without WordPress account or send the entire site for review!
No, Flow is a tool dedicated for WordPress and it just needs access to the admin dashboard. No SaaS subscription, no external tools.
*.l10n.php translation file now declares a direct-access guard, resolving a Plugin Checker warning.font-family: "<post title>" instead of the real font name.<a> (gallery markup) no longer collapse to their intrinsic size.<a><img></a> markup now opens the comment popover when clicked instead of being swallowed by the review-page link guard.onclick="window.open( '…', '_self' )" handlers (common in galleries) no longer navigate the review iframe out of the chrome — same _blank bypass as target="_blank" anchors..entry-content / .wp-block-post-content.assets/blueprints/blueprint.json so the WordPress.org plugin page can spin up a one-click demo of the review experience (logged in as a reviewer with sample image/video content to comment on).template_include (e.g. Kallyas builder, other site-builder themes), so the dedicated review page renders correctly regardless of the active theme.button / [type=button] selectors.languages/, plus Domain Path header, so translate.wordpress.org community translations are picked up automatically.react-jsx-runtime script handle that core only registers from 6.6 onwards, restoring the review page chrome and editor sidebars on older WP versions.