Google Calendar Events (the predecessor to Simple Calendar, still in use on many sites) pulls events from Google Calendar feeds and renders them on the front end. Each feed is stored as a custom post type with a cached event payload keyed to the feed. The admin lists the feeds and offers a shortcode per feed; the events themselves never get an admin surface.

SleekView reads the feed CPT and the cached events and turns them into a real grid. Title, source feed, start date, end date, and category sit as real columns on one screen. Saved views split the work by feed, by category, or by date range, and the table reads from the same cache the public shortcode renders.

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

Google Calendar Events is intentionally a thin bridge between Google Calendar and the front-end shortcode. That minimalism is its strength for visitors, who see a tidy public calendar. It is also why content teams struggle to plan against it.

The cached payload already contains every event the public site renders, but the admin only lists feeds, so volume and category spread stay invisible to the team that needs to plan around them. Treating events as real rows in a sortable, filterable grid turns the legacy admin 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.