SleekView Kanban for Edit Flow
SleekView Kanban reads posts straight from the WordPress database, groups them into the Edit Flow custom statuses your newsroom already uses, and lets editors drag stories across lanes from pitch through assigned, draft, and pending review without ever leaving WordPress.
♾️ Lifetime License available
Why Edit Flow newsrooms need a kanban view
Edit Flow extends the WordPress post status system with custom values like pitch, assigned, draft in progress, and pending review, and stores every story as a standard post with that status set on the row. The default editorial calendar is great for date planning, but the post list screen still treats every story the same way regardless of where it sits in the editorial pipeline. That is fine for a small blog. It falls apart for a newsroom running thirty open stories across five editors.
SleekView Kanban reads the same WordPress posts and groups them by the Edit Flow post_status value, which is the natural pipeline column for this plugin. Each card surfaces the story headline, the assigned writer, the editor in charge, and a relative time stamp so the editor in chief can scan a column without opening every story. Spiked and on-hold pieces sit in their own lanes instead of cluttering the active pipeline.
Dragging a card from one column to another writes the new custom status back to the same post, so the Edit Flow calendar, story budget reports, and notification rules all stay in sync. Bulk drags update every row in a single transaction, so a stack of fifty pitched stories can be moved into assigned in one sweep without a hundred separate clicks through the post list.
Workflow
From editorial calendar to kanban in four steps
Point SleekView at Edit Flow
Pick post status as the kanban column
Choose what shows on each card
Turn on drag-and-drop writes
Sample board
Sample newsroom editorial board
Comparison
Default post list vs SleekView Kanban
Default WordPress post list
- Flat post list filtered by status with no instant view of the entire pipeline at once
- No visual sense of how many stories are stuck in draft or pending review at a glance
- Status changes require opening each story, scrolling to the status box, and saving
- Bulk actions only support trash and basic edit with no card-style preview of stories
- Mobile editors get the same dense WordPress post table with painful horizontal scroll
SleekView Kanban
-
Groups posts by Edit Flow custom
post_statuswith live counts per lane - Drag a card between lanes to write the new status back to the post in one update
- Card fronts surface headline, writer, editor in charge, and target publish date
- Spiked and on-hold stories sit in their own lanes so the active newsroom stays clean
- Capability-aware drops respect WordPress roles so writers cannot publish to live
Features
What SleekView Kanban gives you for Edit Flow
Native Edit Flow status support
SleekView reads every Edit Flow custom status registered on the site directly, including the order and color you set in the editorial admin. Pick exactly which fields show on the card front, which open in a side panel, and which stay hidden but searchable from the filter bar above the board.
Drag to change story status
Every drop writes the new custom post status back to the post in a single update. Edit Flow notifications, the editorial calendar, and any story budget report that reads the status field stay in sync, so a card move never produces a ghost story or duplicate notification email.
Filter by writer, editor, or section
A filter bar above the board narrows lanes by writer, editor in charge, or section taxonomy. Saved filters are per-user, so each editor keeps a focused board on the desk they own while the managing editor can pull up the entire newsroom from the same WordPress posts.
Audience
Three teams using the Edit Flow kanban
Newsroom managing editors
Managing editors pin the board to the full pipeline and watch how many stories are moving through pitch, draft, and review across every desk in one screen, instead of paging through the post list.
Section editors with their own desks
Each section editor opens a board filtered to their desk, sees what is in draft and what is waiting on review, and moves cards forward themselves without pinging the managing editor for every status change.
Editors clearing review backlogs
Editors use the pending review lane to surface stories that have been waiting too long, drag them back to draft for revision, or move them forward to scheduled when they are ready to publish.
The bigger picture
Why a kanban beats a list for editorial
Editorial work is a pipeline, not a database. Edit Flow ships exactly the right primitives, custom post statuses and a clean editorial calendar, but the WordPress post list screen treats every story the same regardless of where it sits in the workflow. A pitch that landed this morning looks identical to a pending review piece that has been waiting on an editor for a week, and a spiked story is just another row in the trash filter.
That works for a small blog. It falls apart in a real newsroom. A kanban board fixes the shape of the data, not just its presentation.
Lanes show how many stories are stuck in each stage right now, drag-and-drop turns status changes into one gesture instead of a post edit, and filters let each editor focus on the desk they own. The same Edit Flow data powers a different mental model, one that matches how real newsrooms actually move stories from pitch to published.
Questions
Common questions about SleekView Kanban for Edit Flow
SleekView reads the WordPress post status registry directly, so every Edit Flow custom status you already use shows up automatically as its own lane. You never have to rebuild the status list, and you can keep editing statuses inside Edit Flow without touching the SleekView config.
Yes. The drag handler updates the same post status field that Edit Flow notifications watch, so notification rules fire exactly as they would if a writer changed the status from the post edit screen, including any custom hooks added by Edit Flow add-ons or your own code.
Yes. SleekView views are configuration only, so you can build one board per desk from the same WordPress posts. Each editor picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole newsroom team.
SleekView reads the post status registry on every load, so a new Edit Flow status shows up automatically as its own lane at the end of the board. You can drag it into the right position in the workflow, assign a color, and decide which fields the lane's cards should surface, without rebuilding the view.
No. The drag handler updates the same post status field that the editorial calendar reads, so the calendar refreshes on the next page load and never drifts from the live state of the kanban board in front of the editor moving cards.
SleekView respects WordPress capabilities, so you can require publish_posts or a custom capability before a card can land in the scheduled or published column. Writers see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently going live.
Each lane uses a virtual scroller, so a published column with thousands of cards still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top narrows large lanes without resetting the scroll position or any cards in motion.
SleekView reads and writes the standard WordPress posts table that Edit Flow already uses. View configuration sits in its own small options table, so uninstalling SleekView leaves every story, status, and editorial calendar entry exactly where Edit Flow wrote it.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout