Google Calendar Events Pro registers each Google calendar feed as a post of the calendar post type, with the credentials and feed configuration in wp_postmeta against that post. Synced event data is cached against the same feed, either in postmeta or in a transient depending on the feed's caching mode. The default WP list shows feed title and last update date; everything else needs the edit screen.

SleekView reads the calendar CPT and exposes the feed-level meta keys (Google calendar ID, time zone, max events, cache duration, category filter) as columns. A second view reads the synced event cache so editors can see which events the feed is currently surfacing on the front end without clicking into each feed.

The grid is the missing operations layer for editorial teams running multiple Google calendars on a WordPress site: filter feeds by status, sort by last-sync time to find stalled imports, and inline-edit the cache duration when an upstream calendar is changing rapidly. Saved views split the work between editorial, who curate the categories shown, and developers who maintain the feeds.

Plugins that sync external data into WordPress always face the same operational problem: the data is in two places, and the system that pulls it in has to be monitored separately from the data itself. Google Calendar Events Pro is a strong implementation of the pattern, with feed configuration as a custom post type and cached events stored against each feed. What its admin does not give editorial teams is a single screen that answers two questions at once: which feeds exist and what are they currently showing on the site.

The default list answers the first question; the second requires clicking into every feed. The moment a site is running more than a couple of Google calendars, the gap matters: a stalled feed silently strips events from a page, a category filter change confuses readers, an upstream calendar deletion leaves cached records that no one notices. Treating both layers as views in the same admin gives editorial a single dashboard for feed health and feed content.

Saved views become the monitoring rituals, and inline edits to cache duration and category filters route through the plugin's existing settings layer so nothing breaks downstream.