Simple Calendar pulls events from Google Calendar feeds and renders them on the front end through a shortcode. The plugin stores each feed as the gce_feed custom post type and caches the resolved event payload in transients keyed to that feed. Organizers see the public list or grid view, but the admin side is the standard WordPress posts table for feeds plus a per-feed editor.

SleekView reads the feed CPT and the cached event payload, surfacing both as chart cards. Total upcoming events, events per feed, events per category, and a weekly cadence area chart sit on one dashboard. Each card refreshes on the same cache cadence Simple Calendar already uses, so charts and the public shortcode never disagree on the data.

The dashboard 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 only reads the already-fetched rows and groups them in the four shapes a planning meeting cares about.

Simple Calendar does one thing well, which is pulling Google Calendar feeds into a shortcode-friendly front-end calendar. That single-purpose design is exactly why a chart layer matters. The cached payload already contains every event the public site renders, but the WordPress admin only lists the feeds themselves, 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 standup glance, a donut of per-feed mix is the planning lens, a bar of top categories is the editorial brief, and a cadence area chart is the early warning for an empty week. None of those are exotic charts; they are the four shapes any organizer would draw in a notebook on a Monday morning. SleekView reads the cached payload, surfaces it as the cards above, and leaves Simple Calendar untouched.

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