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. Divi regenerates its static CSS cache, other caching plugins invalidate, and analytics tied to publishing react exactly as if a designer moved the layout through the regular Divi admin screen for that library item.

Yes. Any taxonomy including the Divi layout category, custom meta field, or the Divi layout type field itself can be the grouping axis. Most teams add a custom design_review meta key for stages like wireframe, design, dev review, qa, and shipped, and group by that instead of post status.

Yes. Divi Theme Builder templates are stored as a related post type and SleekView reads them the same way as library items. You can run separate boards for the library and theme builder, or combine them into one design pipeline board covering every reusable Divi layout on the site.

Scheduled layouts appear in their own Scheduled column by default with the queued publish time shown on each card. Moving a scheduled layout 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 on the live site.

Yes. Every action on a card uses the same capability checks as the standard Divi editor, so designers without publish capability cannot drag cards into the Published column. Any role plugin you already use controls who can drag between which columns on the board view of the library.

The post status changes back to draft through wp_update_post, which triggers the usual unpublish path. The layout disappears from frontend rendering on the next request, Divi static CSS regenerates, cached page versions are invalidated, and the original publish date is preserved so republishing later keeps the canonical URL.

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 layout 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 designer sees the change land in near real time without refreshing the view manually.