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 chart cards. Total upcoming events, events per feed, top categories, and weekly cadence sit on one dashboard. Each card refreshes on the cache cadence the plugin already uses, so chart and shortcode render the same payload.

The dashboard 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 groups them in the four shapes the team behind the calendar actually plans 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, but the admin only lists feeds, so the volume, the category spread, and the cadence stay invisible to the team that needs to plan around them. A KPI of upcoming events is the morning glance, a donut of per-feed mix is the planning lens, a category bar is the editorial brief, and a cadence area is the warning for an empty week. SleekView reads the cached payload, surfaces it as the cards above, and leaves the plugin untouched.

The shortcode stays the public view. The dashboard becomes the admin's companion.