Yes. SleekView reads the venue name and address meta the Google Maps add-on writes onto event_listing posts and lets you choose any of those values for the card front. Latitude and longitude are also available as card fields if you need to spot rows that failed to geocode.

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

Yes. SleekView can filter event_listing rows where _event_location_lat or _event_location_lng meta is missing or set to zero, and surface those rows in a separate filtered board view. Editors can spot the failed rows before publishing and fix the venue address from the editor screen.

Yes. SleekView reads any custom listing field you configured through WPEM hooks 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 separately in the database.

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 event_listing data does not change, only what each role reads on the board.

Yes. WPEM registers an expired post status for past events, and SleekView reads the distinct status values and renders an Expired column next to the built-in ones. The scheduled cron that flips past events into that status keeps running, and the board reflects the change on the next refresh.

Yes. SleekView reads the live event_listing meta on every load, so the next time the Google Maps add-on re-geocodes a venue address and writes a new latitude and longitude pair the board reflects the new values on the next refresh. There is no separate index to rebuild for venues.

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