Google Calendar Events stores every connected Google feed as a gce_feed custom post type with the calendar ID and the API credentials. Fetched events are cached per feed with the summary, start time, end time, location, organiser, and Google event status (confirmed, tentative, or cancelled). The plugin renders the feed on the frontend as a grid or list. There is no native admin board view of the cached events.

SleekView reads the gce_feed posts and the cached event payloads as a single dataset. Each row becomes one Google occurrence with the feed name, calendar ID, start time, location, organiser, and Google status. Flip the view to Kanban and pick the Google event status as the group column for a confirmed and tentative split, or pick the source feed for a multi-team board. The card front shows the summary, the start time, the location, and the organiser.

Write-back is off by default because the source of truth lives in Google. The default board is a read-only view on top of the cached events, refreshed when the Google Calendar Events feed refreshes. With write-back on, SleekView calls the same Google API the plugin already uses to update the event status or move it between calendars, with the credentials stored on the gce_feed post.

Plenty of teams already run their calendars in Google. Google Calendar Events pulls those feeds into WordPress and renders them on the frontend, which is the right answer for a public site. The gap is internal.

An ops team wants to see across feeds at a glance, an event coordinator wants tentative events visible, and a community manager wants external and internal feeds visually separated. The plugin admin does not provide any of that. SleekView reads the same cached Google payloads, groups them by source feed or by Google event status, and lets the team work on a real board while Google stays the source of truth.

With write-back off the board is safe by default, with write-back on it uses the same credentials the plugin already stores on the gce_feed row. Either way the team finally has a board for the calendar they were already running.