All-in-One Event Calendar already tracks every event as a row. Events land as ai1ec_event custom posts with standard WordPress post_status values like draft, pending, publish, private, and trash, plus the plugin's own meta for start, end, venue, and recurrence. The default Events admin lists those records as a long table sorted by event date, with the status visible only as a small label per row.

SleekView Kanban reads the same ai1ec_event posts and groups them into columns by status. The natural grouping field is the publishing state, so the board shows Draft, Pending review, Published, and Cancelled as separate stacks. Each card surfaces the event title, the start datetime, the venue, and any custom field your editorial workflow has added, so the front of the card carries the data the editor and the producer actually need.

Dragging a card writes the new status back to the source row. Moving a Draft into Pending review notifies your editor, moving into Published makes the event visible on the front-end calendar instantly, and moving to Cancelled (a custom status the board can register) flips the event without losing the original record. SleekView keeps an audit log per card so editorial changes made on the board are traceable back to the user who made them.

An event programme has stages and people move through them. Drafts get assigned, editors approve copy, producers confirm venues, and occasionally a weather call or a venue clash pulls an event back to Cancelled. All-in-One Event Calendar stores all of that already in ai1ec_event posts and the related meta, but the default admin is still a long table sorted by event date with status as a small column.

Seeing how many drafts are waiting on an editor, how many approved events still need a venue confirmation, and how many of last month's cancellations need a refund note takes a filter, a sort, and a count in your head. SleekView Kanban turns the same data into a board with Draft, Pending review, Published, and Cancelled as columns, a count per column at the top, and a card per event with the fields the editorial and venue teams actually read. Drag a card to flip the status and the post updates on the row.

The events admin, the public calendar, and any subscriber email list all read the new value because SleekView writes to the source row, not to a parallel table.