The drag calls the standard WordPress post update API so the change is persisted to wp_posts and triggers the usual transition_post_status hook chain. Caching plugins, CDN purges, and any analytics tied to publishing react exactly as if an editor moved the post through the regular admin screen.

Yes. SleekView accepts a content filter that scans post content for the markup Simple Lightbox treats and excludes everything else, so the board never gets cluttered with plain text posts that have no lightbox treatment to manage in the first place.

Yes. Any taxonomy, custom meta field, or author assignment defined on the host post type can be the grouping axis. Most teams add a custom media_review meta key for review steps like image review, alt text check, captions done, and approved, and group by that field.

Scheduled posts appear in their own Scheduled column by default with the queued publish time shown on each card. Moving a scheduled post back to Draft clears the publish timestamp, and moving it forward to Published immediately fires the publish hook so any downstream integrations run right away.

Yes. Every action on a card uses the same capability checks as the standard post edit screen, so contributors cannot publish, editors cannot trash other people content unless their role allows it, and any role plugin you already use controls who can drag between which columns.

The post status changes back to draft through wp_update_post, which triggers the usual unpublish path. The post disappears from frontend listings on the next request, cached page versions are invalidated by your caching plugin, and the original publish date is preserved as the post date so republishing later keeps the canonical URL intact.

Yes. The kanban surface uses pointer events so it works with mouse, trackpad, touch, and pen input. Long press on a card initiates the drag on touch devices, and column scrolling works even while a card is mid drag so you can move a post across columns that do not fit on the same viewport.

Each card drag is a single atomic post update so two simultaneous drags resolve in the order the server receives them, with the second drag winning. The board polls for status changes every few seconds so the other editor sees the change land in near real time without refreshing the view.