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. Brizy regenerates its compiled assets, caching plugins invalidate, and any analytics tied to publishing react exactly as if a designer moved the template through the regular Brizy admin screen.

Yes. Any taxonomy, custom meta field, or the Brizy global block type 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 the raw post status field on the template entry.

Yes. Brizy global blocks live in the same brizy_template post type as page templates and SleekView reads both the same way. You can run separate boards for global blocks and for page templates, or combine them into one master design pipeline board covering every Brizy asset on the site.

Scheduled templates appear in their own Scheduled column by default with the queued publish time shown on each card. Moving a scheduled template 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 Brizy 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 kanban board view of the library.

The post status changes back to draft through wp_update_post, which triggers the usual unpublish path. The template disappears from frontend rendering on the next request, Brizy regenerates compiled assets, cached page versions are invalidated, and the original publish date is preserved 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 template 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.