Simple Calendar pulls events from Google Calendar feeds and renders them on the front end through a shortcode. Each feed is stored as the gce_feed custom post type, and the resolved event payload is cached in transients keyed to that feed. The admin lists feeds but never the events; visitors see the public list or grid view, while organizers planning the month rely on whatever spreadsheet they keep on the side.

SleekView reads both the gce_feed posts and the cached event payload. Title, status, source feed, start date, and category sit as real columns on the same grid, so the team running the calendar can scan the month without loading the shortcode in another tab. Saved views split the work by feed, by category, or by date range, and the table stays in lockstep with the cache the public shortcode reads from.

The grid does not change how Simple Calendar fetches from Google Calendar. The plugin still owns the API request, the cache window, and the front-end render. SleekView reads the rows the plugin already wrote and turns them into a table editors and content leads can plan against.

Simple Calendar does one thing well: it pulls Google Calendar feeds into a clean public shortcode. That single-purpose design is exactly why a table layer matters in the admin. The cached payload already contains every event the public site renders, but the WordPress admin only lists the feeds themselves, so volume, category spread, and cadence stay invisible to the team that needs to plan around them.

Treating events as real rows in a sortable, filterable grid turns the calendar from a public-facing display into a planning surface. Saved views become the rituals of the role (Friday newsletter pick, Monday category check, weekly cadence review), and the team spends less time loading shortcodes in different tabs to discover what was already in the cache.