PublishPress adds custom statuses, editorial metadata (deadlines, assignments), and notifications on top of WordPress's native post workflow. Data stays in wp_posts for the posts themselves, wp_postmeta for editorial metadata, and PublishPress-specific tables for notifications and editorial comments. The calendar and notifications UIs are excellent, but a tabular portfolio view ("every draft per writer, every custom status, every deadline") needs columns that the default post list doesn't show.

SleekView reads the editorial metadata directly and exposes assigned writer, due date, custom status, and editorial comment count as proper columns. A single portfolio view shows title, assignee, status, due date, and last editorial comment in one row. Filters combine assignee with status and a date window so an editor-in-chief can see "every Lena draft past due" or "every pitch in the queue for over two weeks" in one screen.

Inline edits to status, assignee, and due date route through PublishPress's update functions so notifications fire and the calendar UI stays in sync. SleekView is admin-only and coexists with the native calendar, notifications, and editorial comments views: the data sits in standard WordPress tables, and there is no separate sync layer.

PublishPress closes a real gap in WordPress: native posts only have draft, pending, and published, and that's not enough vocabulary for serious editorial teams. Custom statuses, deadlines, editorial comments, and structured notifications turn WordPress into a workable editorial CMS. The interfaces PublishPress ships (the calendar, the notifications screen, the editorial comments meta box) are good at their specific jobs, but none of them is a portfolio view.

An editor-in-chief wants a list of every in-progress piece with assignee, status, due date, and recent activity in one screen, and that view doesn't exist by default. People recreate it in spreadsheets, kept in sync by hand, which is exactly the kind of duplication PublishPress was supposed to remove. SleekView restores the missing layer.

The same custom statuses, the same editorial metadata, the same comments, but now as a sortable, filterable table that updates through PublishPress's own functions. The calendar still owns dates; the portfolio finally owns the editorial overview.