Timely Pro runs on the AI1EC engine. Events live as ai1ec_event custom post types and recurrence metadata sits in the wp_ai1ec_events table with start, end, recurrence rule, and venue id. The default Timely dashboard is built around the calendar widget, which is great for visitors but leaves admins clicking through event edit screens to manage a real recurring schedule.

SleekView reads the ai1ec_event CPT joined to wp_ai1ec_events so each event row carries its start, end, recurrence rule, all-day flag, and category. Inline edits route through the AI1EC abstraction so the calendar stays in sync, and the recurrence rule itself remains editable as a structured field rather than a raw RRULE string.

The day-to-day workflow becomes a planning surface: filter to next month, group by category, sort by recurrence frequency. Marketing pulls a CSV of every weekly recurring event for the newsletter, the operations team flags the events that need venue confirmation, and the editor sees what's draft versus published from one grid.

Timely Pro's public calendar widget is the best part of the plugin for visitors, and the worst part for admins trying to plan a season. A widget is a presentation layer, not a workflow surface. Programme managers running ten or twenty events a month need to see recurrence, status, venue, and category in one row, not click into each event edit screen to discover the schedule.

The data is already there: ai1ec_event CPT, wp_ai1ec_events recurrence table, venue and category taxonomies. SleekView turns those tables into the planning surface the role actually needs, with saved views per persona and inline edits that route through the same AI1EC abstraction the public calendar reads. The widget stays where it belongs (in front of visitors), and the admin moves into a grid that matches how programmers actually think.