Yes. Moving a card calls wp_update_post and the Duplicate Post Republish helper when republishing, the same functions the admin uses, so transition_post_status hooks fire normally and the original post receives the refreshed content through the standard plugin pipeline without any extra plugin glue.

SleekView reads the WordPress posts table directly, filters to posts with the _dp_original meta, and joins the original post title and category 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 duplicate.

Yes. SleekView ships with role-based permissions, so refresh leads can have a single page that holds the duplicate board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so writers cannot republish their own duplicates without an editor's move.

Standard duplicates without Republish also appear on the board, simply with a different state lifecycle. SleekView reads distinct values from the chosen field, so a plain duplicate workflow that ends in Published works the same as the Republish flow, with the original post left untouched at publish time.

Yes. Each board has one source so the rules stay clear, and a single duplicates board with Cloned, In rewrite, Scheduled, and Republished columns covers most refresh programs. Teams running parallel refresh tracks add a second board grouped by section taxonomy for a desk-specific view.

Dragging never deletes data. It changes the state field SleekView is grouping by, which matches what the editor does through the Publish dropdown. Republishes use the standard Duplicate Post helper to merge content into the original post, so the original URL and any backlinks continue to work.

Yes. Each card can show the time since the duplicate was created or last modified, so a clone 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 refresh 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 _dp_original meta filters. Sites with tens of thousands of duplicates stay responsive because heavy fields are only fetched for cards currently on screen.