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

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

Yes. All Bricks template types live in the same bricks_template post type and SleekView reads them the same way. You can filter the board by template type or run separate boards for each template type if your team has dedicated designers for headers, footers, archives, and singular pages.

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 Bricks editor, so users without the Bricks edit capability cannot drag cards on the board. Any role plugin you already use controls who can drag between which columns on the board view of the Bricks template 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, Bricks regenerates CSS, cached page versions are invalidated, and the original publish date is preserved so republishing later keeps the canonical URL intact for SEO purposes.

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.