Yes. SleekView reads post_status from spiffy_event posts and renders one column per distinct value with the human label WordPress uses. Draft, pending, publish, and any custom status the Spiffy plugin registered for expired or recurring all show as their own columns on the board.

Yes. Dropping a card into Published writes the new post_status to the spiffy_event row through the same code path the editor sidebar uses, so the WordPress transition_post_status action fires and the author receives the standard publish email exactly as if you clicked publish in the editor.

Yes. SleekView reads any custom meta you configured on the Spiffy event form and lets you choose it for the card front. The value matches what shows in the event editor because SleekView reads the same meta the editor reads, not a copy stored somewhere else in the database.

Yes when you register an expired status through the Spiffy plugin settings or a snippet. SleekView reads the distinct status values and renders an Expired column next to the built-in ones. A scheduled cron can flip past events into that status and the board reflects the change on the next refresh.

Yes. Saved kanban views are scoped per role and per capability, so contributors see Draft and Pending review filtered to their own author ID, while editors see every author across the columns. The underlying spiffy_event data does not change, only what each role reads on the board.

Yes. The board can show every spiffy_event post across all categories, or be filtered to a single category by taxonomy slug for a per-category editor view. The grouping field stays post_status, only the filter changes per saved view for each editor or admin.

Yes. SleekView reads the live spiffy_event rows on every load, so changes made through quick edit on the all events screen show up on the board on the next refresh. The board does not maintain a parallel index because it reads the same posts the editor reads directly from the database.

No. SleekView paginates inside each column and loads card detail on demand, so a calendar with several thousand events renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before the board even renders.