WP Meetings registers a meeting custom post type with start and end meta, a host user ID, an attendees list, an agenda field, and a meeting status meta key that typically holds scheduled, in_progress, completed, or cancelled. The standard WordPress post_status still controls whether the meeting record is published or private. The default admin screen is a list table sorted by date with a status filter dropdown.

SleekView reads the meeting post type and joins the meeting-status meta, the host user lookup, and the attendees list. Flip the view to Kanban and pick the meeting-status meta key as the group column. SleekView builds columns for Scheduled, In Progress, Completed, and Cancelled and renders one card per meeting with the title, the start time, the host display name, and the attendee count on the front. Long agendas stay in the detail drawer so the board front is scannable.

Drag a meeting from Scheduled to In Progress and SleekView updates the meeting-status meta through update_post_meta, then fires a standard WordPress action hook so any WP Meetings notification or calendar sync that already listens for status changes runs the same way as it would from the admin screen. Recurring meetings show the parent series row so the board does not get spammed with every weekly instance.

Every WP Meetings install ends up with the same shape of data. There are meetings scheduled for the next week, a few happening right now, a long tail of completed meetings, and a handful of cancellations. The default admin presents that as a list table with a status dropdown, which works for editing a single meeting and falls apart for any coordinator trying to see the whole programme.

SleekView reads the same meeting post type and turns the status meta into real columns. The team sees what is on today, what is queued for the week, what is finished, and what was cancelled. Hosts can pull a board scoped to their own meetings.

Coordinators can group by host to balance load. Drag and drop writes back through update_post_meta and fires the same hooks the admin uses, so notifications and calendar syncs keep running normally on every move.