ACF Pro Extensions adds extra field types and admin tools on top of ACF PRO, including additional Select, Radio, and Repeater patterns that site builders use to model review queues. Records live as posts of the custom post type registered through the ACF or extension UI, with field values in wp_postmeta keyed by the ACF field configuration, so the data shape is familiar and predictable across many sites.

SleekView Kanban points at the ACF-backed post type, lets you pick the column that holds the review state to group by (an ACF Select or Radio field, a derived review_state built from several ACF fields, or the standard post_status when the workflow needs publish-driven lifecycle), and renders one card per record. Each card shows the record title, the assignee, the due date, the related post via an Advanced Link field, and the modified timestamp so the team sees the review shape at a glance.

When a reviewer drags a card from Pending into In review, Approved, or Published, SleekView writes the new value through the standard ACF update_field function, fires the ACF save hooks, and updates the queue counts at the top of each column. The Published column doubles as a review history view so old ACF records stay searchable without cluttering the Pending board across the active queue.

ACF Pro Extensions is where site builders go to model parts of the business that WordPress does not model out of the box, with extra field types layered on top of the familiar ACF PRO surface. Case studies, vendor profiles, knowledge base articles, and many more entity types live as ACF-backed custom post types. The default admin still shows them as flat lists with extra columns, which means review stage only lives in people's heads or in a separate spreadsheet that nobody updates after the review.

A kanban view changes that shape. Any ACF Select field becomes the columns, the most important ACF fields land on the cards, and the board gives every model a real review surface without writing a custom admin page. The In review column becomes the work, the Published column doubles as the searchable inventory, and the Approved column makes the handoff visible across the team.

Moving cards keeps update_field in play, so ACF save hooks and any audit or notification plugin stay correct after every move. The work feels small because each card is small, and the board makes the size of every queue honest across every model the team manages.