SleekView for Tasks by PublishPress
SleekView reads the Tasks by PublishPress task post type along with status, assignee, due-date and linked-post meta, then renders every editorial task across the whole site as a sortable, filterable, inline-editable table.
♾️ Lifetime License available
Editorial tasks live one post at a time, the table view sees them all
Tasks by PublishPress is the editorial task add-on of the PublishPress family. Tasks attach to posts as a custom post type with meta for status, assignee and due date, and the plugin surfaces them in a sidebar on the post editor and in a simple admin list. For a single managing editor running a few posts, that is enough. For a newsroom or content team running dozens of pieces in parallel, the data lives in the right shape but the surface does not show it.
SleekView reads the same task post type and meta and renders it as a cross-pipeline editorial table. Status, assignee, due date and linked post become first-class columns. Sorts work the way a managing editor expects: due date ascending, status grouped, assignee for a per-person view. Filters compose, so "open tasks assigned to Priya due this week" is one composed view, and "every overdue task across the issue" is another. Inline edits on status and assignee route through the standard WordPress save path, so PublishPress hooks fire exactly the way they would from the editorial sidebar.
PublishPress keeps owning the workflow, the notifications and the editorial integration. The table view adds the cross-pipeline cockpit the sidebar was never built to be.
Workflow
How SleekView surfaces Tasks by PublishPress data
Point at the task post type
Pivot meta into columns
Compose the columns
Save per-role views
Sample columns
A typical Tasks by PublishPress editorial view
wp_posts
| Title | Status | Assignee | Due date | Linked post | Modified |
|---|---|---|---|---|---|
| Sub-edit cover feature | In review | Priya Shah | 2026-05-18 | Cover story: spring rebuild | 2026-05-15 |
| Source quotes for tech piece | In progress | Daniel Ruiz | 2026-05-20 | AI coding tools review | 2026-05-14 |
| Fact-check legal column | Blocked | Maya Chen | 2026-05-12 | Privacy column May | 2026-05-13 |
| Schedule social preview | To do | Daniel Ruiz | 2026-05-22 | Cover story: spring rebuild | 2026-05-11 |
| Final copy pass | Done | Priya Shah | 2026-05-05 | AI coding tools review | 2026-05-06 |
Comparison
Default Tasks by PublishPress admin vs SleekView
Default Tasks by PublishPress admin
- Sidebar surface scopes tasks to one post at a time
- Per-editor load needs a manual count from the admin list
- Sorting by due date or filtering by status combination is not first-class
- No saved "overdue editorial work" view across the whole site
- Composing filters on assignee, status and linked post needs custom SQL
SleekView
- Status, assignee, due date and linked post as first-class columns
- Sort by Due date ascending to expose overdue editorial tasks
- Filter by Linked post to scope every task on a single piece
- Saved views per role: managing editor, contributor, copy editor
- Same dataset feeds the editorial table and the chart dashboard
Features
What SleekView gives you for Tasks by PublishPress
Editorial cockpit
Title, Status, Assignee, Due date and Linked post become first-class columns. Stand-ups open on a real table instead of clicking through twelve posts.
Per-editor scoping
Filter by Assignee and the table scopes to a single editor or contributor. Reassignments and hand-offs become data-backed conversations during a busy issue cycle.
Overdue triage
Filter to Due date before today and Status not Done, save the view, gate it by role. The editorial team has a permanent triage queue ready for a focused sweep.
Audience
Who uses SleekView for Tasks by PublishPress
Managing editors
Pin a stand-up view sorted by Due date with Linked post grouped. The editorial morning opens on the same screen every day instead of clicking through posts.
Newsroom leads
Filter by Assignee and Priority to balance load across writers and copy editors during an issue cycle. The over-loaded editor stops being a deadline-day surprise.
Contributors
Filter the same table to a single Assignee for a personal queue. "What is on my plate this week" becomes a saved view, not a saved search.
The bigger picture
Why editorial workflows need a cross-pipeline table
Editorial workflow plugins solve the per-post layer well and the cross-post layer poorly. Tasks by PublishPress stores the data perfectly: each task has a status, an assignee, a due date and a link to the post it belongs to. The sidebar surface answers "what is left on this post".
The table view answers "what is left on the issue, what is overdue, who is overloaded, what is blocking us this week". Those are different questions and they need a different shape. SleekView adds that shape without changing how PublishPress works.
Sorts and filters compose, inline edit routes through the normal save path, and editorial leadership finally has the cockpit the data was always asking for.
Questions
Common questions about SleekView for Tasks by PublishPress
No. SleekView reads the PublishPress task post type and meta. The plugin continues to own task creation, status changes, notifications and the editorial integration; SleekView adds a composable editorial table on top of the same records.
 Yes if the linked-post relation is stored as meta on the task. Sort by Linked post to group every task on a single piece, or filter to one post to scope the entire table to that piece's outstanding work.
 Yes. Filter to Due date before today and Status not Done, and the table narrows to the overdue queue. Save that view and the editorial lead has a permanent surface to assign cleanup against.
 Yes. PublishPress Planner, Checklists, Capabilities and Revisions each own their own post types or meta. SleekView can read the task data on its own table, then sit alongside other SleekView tables for those plugins on the same admin.
 Inline edits route through the standard WordPress update path, the same one PublishPress hooks listen to. Changing status or assignee inline fires the same actions as saving in the editorial sidebar.
 Yes. Filter by Assignee and the entire table narrows to that person's tasks. Useful both for individual contributors checking their week and for managers reviewing one editor's load before a one-on-one.
 Yes. Any filtered view exports to CSV with the columns the table shows. Editorial retrospectives and weekly reviews get a spreadsheet of tasks with statuses and assignees attached.
 No. PublishPress still owns the editorial workflow, the sidebar surface and the notifications. SleekView adds a composable editorial table on top of the task data, designed for cross-pipeline questions the per-post sidebar was not built to answer.
 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