Spiffy Calendar keeps things deliberately minimal: events live in a dedicated table (commonly wp_ajde_events) with title, dates, category, author, and recurrence stored row by row. The plugin's admin shows the list and the month grid; reporting is not part of its remit.

SleekView Charts reads the Spiffy events table directly. Category, author, event date, and recurrence type promote to columns that any chart can group or aggregate on. The dashboard answers questions a minimal plugin does not try to: events per author, category balance, monthly cadence, recurrence usage.

Because reads use standard SleekView dataset connectors, custom columns or extensions added to the Spiffy table appear automatically. The chart dashboard sits alongside the table and kanban views built from the same dataset.

Spiffy Calendar is a deliberately minimal plugin and that minimalism is part of why people pick it: a lean schema, a fast admin, and no feature bloat. The trade-off is the reporting layer, which the plugin simply does not have. A community manager who wants to see contributor activity, a librarian who wants to see category mix, a coordinator who wants to see monthly cadence all run out of admin support after the first question.

SleekView Charts treats the Spiffy table as a normal SleekView dataset and renders a four-card dashboard answering exactly those questions. Saved views become the rituals of the role. The plugin keeps owning the calendar; SleekView just makes the reporting layer match the work the team actually does.