Spiffy Calendar Pro stores events in its own spiffycal_events table rather than as posts, with category links and recurrence patterns in associated meta. The default admin shows a paginated list of events with title and date, which is fine until a site is managing dozens of recurring series across multiple categories.

SleekView reads spiffycal_events directly and promotes start, end, category, recurrence rule, and any custom event field to first-class columns. Inline edits route through Spiffy Calendar's CRUD layer where supported, with conflict-detecting direct writes as a fallback for fields the plugin's CRUD does not expose.

The grid replaces the per-event drilldown with a planning surface. Filter by category to see the upcoming workshop schedule, sort by recurrence pattern to audit the series that drive the most visibility, save views per editor. Exports run against the filtered set so a category-aligned CSV is ready for newsletter prep without manual culling.

Spiffy Calendar Pro is uncommon among WordPress event plugins in that it writes events to its own table rather than reusing the post type. That choice pays off for query performance, but the default admin only surfaces the columns that the original Spiffy Calendar design needed: title, date, and status. The dimensions a coordinator actually plans around, category and recurrence, sit in linked tables that the default list view never joins.

The cost is the same pattern visible in every event plugin: events end up planned in a spreadsheet because the in-product view does not carry the columns that decide the week. Treating spiffycal_events as a real grid that joins category and recurrence promotes those dimensions to first-class columns. Saved views become the planning rituals, recurrence audits become a sort rather than a per-event drilldown, and category-aligned exports replace the manual culling that marketing currently does by hand.

The data is already in the right shape; the gap is operational, and the grid closes it.