Yes. Moving a card calls wp_update_post, the same function the editor uses, so transition_post_status hooks PublishPress listens to continue firing. Bylines, editorial workflow notifications, and any custom code listening to the standard WordPress hooks keep running without any extra plugin glue or workarounds.

SleekView reads the WordPress posts table directly and joins the PublishPress Authors taxonomy in the same query. You pick the posts table as the source, choose the editorial state field to group by, and SleekView renders one card per post with every byline term shown on the card front.

Yes. SleekView ships with role-based permissions, so editors can have a single page that holds the newsroom board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot publish their own drafts without an editor's review move on the board.

Custom workflow states appear automatically because SleekView reads distinct values from the chosen field. You can group by the workflow plugin's state meta, rename column headers, pick colors, and decide whether editors can drag cards between any two columns or only along the official editorial workflow.

Yes. The PublishPress Authors taxonomy treats both as terms, and SleekView shows each term's display name on the card. Dragging never touches the byline taxonomy, so guest author profiles stay linked to the post and the front-end multi-author rendering continues to work exactly as before for every reader.

Dragging never deletes data. It changes the editorial state field SleekView is grouping by, which matches what the editor does through the Publish dropdown. Author terms live in a separate taxonomy and are not touched by SleekView, so multi-author rendering keeps working across every column move.

Yes. Each card can show the time since the post was last modified or last reviewed, so a draft that has been sitting for days looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column so stale review work never silently drifts out of view.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the posts table for the status filter. Newsrooms with hundreds of thousands of posts stay responsive because byline taxonomy joins are only fetched for cards currently on screen during a review session.