All-in-One Calendar (Time.ly) keeps every entry as an ai1ec_event custom post type with a parallel ai1ec_events instance table holding start, end, venue, contact_name, contact_email, and a recurring rule. Taxonomies cover event categories and tags. The standard WordPress post_status field controls publication, and the Manage Events screen is a paginated list with status filter pills above it.

SleekView reads the ai1ec_event post rows and joins the ai1ec_events instance table for start, end, venue, and contact. Flip the view to Kanban and pick post_status as the group column. SleekView builds one column per status, draft, future, publish, and private, and renders one card per event with the title, the start date, the venue, and the contact on the front. The event category taxonomy stays available in the detail drawer.

Drag an event from Draft to Future and SleekView updates the row through wp_update_post, which fires transition_post_status and save_post so any All-in-One Calendar cache and ICS export refreshes on the next render. Recurring events expose the parent row only, so the board stays one card per series.

All-in-One Calendar has a solid data model. The ai1ec_event post type and the ai1ec_events instance table cleanly separate the editorial side from the schedule side. The Manage Events screen, though, is the same WordPress list table the rest of the admin uses, so editors always lose context the moment they need to see across stages.

SleekView reads the same rows, joins the instance table for venue and contact, and turns post_status into real columns. Editors see what is stuck in Draft. Marketing sees what is queued for the month.

Site owners keep private events visibly separate. Drag and drop writes back through wp_update_post the same way Quick Edit does, hits the same capability checks, and fires the same save_post hooks that already drive cache and ICS refreshes. The board does not replace the calendar, it adds the pipeline view the admin grid never had.