Yes. Moving a card calls wp_update_post, the same function the editor uses, so transition_post_status hooks PublishPress Series listens to continue firing. Series rendering on the front end, navigation between parts, and any workflow plugin listening to the same hooks keep running through the normal pipeline.

SleekView reads the WordPress posts table directly and joins the PublishPress Series taxonomy and the part order meta in the same query. You pick the posts table as the source, choose the state field to group by, and SleekView renders one card per part with the series term and order shown on the card front.

Yes. SleekView ships with role-based permissions, so series leads can have a single page that holds the planning board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so writers cannot publish their own parts without a series lead approving the publish move.

Yes. Each board has its own filter, so you can run a board scoped to a single series taxonomy term for a focused planning view. Series leads often run one general board for the full plan and a per-series board for the active campaign or course on the same dashboard side by side.

Yes. Outline placeholders are simply posts with an outline status, either the default WordPress draft or a custom outline state from a workflow plugin. SleekView reads distinct values from the chosen field, so any custom outline status appears as its own column without any extra plugin glue.

Dragging never deletes data. It changes the post_status field SleekView is grouping by, which matches what the editor does through the Publish dropdown. Series taxonomy assignment and part order meta are not touched by SleekView, so the series rendering keeps working across every column move.

Yes. Each card can show the time since the post was created or last modified, so an outline that has been sitting for weeks looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column so stale planning 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 and series taxonomy filters. Sites with thousands of series posts stay responsive because heavy fields are only fetched for cards currently on screen during planning.