SleekView Kanban for Spiffy Calendar
Spiffy Calendar stores entries in its own spiffy_calendar table with event_begin, event_time, event_title, category_id, and author. SleekView reads those rows, groups them by category or status, and shows one card per event with the date and the organiser on the front.
♾️ Lifetime License available
Read Spiffy events as a board, not as a calendar grid
Spiffy Calendar keeps every event in its own table, usually wp_spiffy_calendar, with columns like event_begin, event_time, event_title, event_desc, event_category, and the WordPress author ID. The admin UI is a month grid plus a separate Manage Events screen with a paged list. Neither view groups events the way an editorial team thinks about them, by category for the marketing calendar or by stage for the publishing pipeline.
SleekView reads the wp_spiffy_calendar table directly, no shortcode required, and lets you pick any column as the group field. Most teams group by event_category for a marketing board or by a custom stage column for an editorial pipeline. SleekView builds one column per distinct value and renders one card per row with the title, the event_begin date, and the author on the front so the board reads as a real schedule.
Drag a card from one category column to another and SleekView updates the event_category column on the underlying row, then refreshes any Spiffy widget output through the same hooks the Manage Events screen uses. Past events stay out of the board unless you opt them in, and recurring events surface only their parent row so the columns do not get spammed with occurrences.
Workflow
From wp_spiffy_calendar to a kanban board in four steps
Connect SleekView to the Spiffy table
Pick the group column
Choose what shows on each card
Enable drag and drop writeback
Sample board
Sample Spiffy Calendar marketing board
Comparison
Default Spiffy admin vs SleekView Kanban
Default Spiffy Calendar
- Manage Events is a paginated list with no grouping beyond a basic category filter
- The month grid view shows events on dates but hides category and ownership context
- No drag and drop to reassign events between categories from the admin screens
- Author and organiser are not surfaced on the main list rows
- No saved views or board mode for editorial pipelines
SleekView Kanban
-
Group wp_spiffy_calendar rows by
event_categoryor any custom column -
Card fronts show event_title,
event_begin, event_time, and author - Drag and drop writes back to the Spiffy table with capability checks
- Saved boards per role for editors, marketing, and ops
- Embed the board on a frontend page with role-scoped access
Features
What SleekView Kanban gives you for Spiffy Calendar
Spiffy fields on the card front
Event title, start date, time, and author from wp_spiffy_calendar and wp_users land on the card front so the board reads like a working schedule, not a generic todo list.
Drag and drop writeback
Moving an event from Webinars to Workshops updates the category column on the Spiffy row through the SleekView writer with the same capability checks the admin screen uses.
Group by any column
event_category gives a marketing board, a custom stage column gives an editorial pipeline, and grouping by author shows workload per organiser on the same dataset.
Audience
Who runs a Spiffy Calendar board with SleekView
Marketing teams
Group events by category to see webinars, in-person events, and workshops side by side in one editable board view.
Community managers
Group by organiser to balance event load across the team and spot who is doing too much in the same week.
Editorial leads
Use a custom stage column to track events from idea to confirmed to promoted across the marketing calendar.
The bigger picture
Spiffy stores the data, SleekView gives it a board
Spiffy Calendar is a lightweight events table at heart. The schema is clean, every event is a row, and the fields are exactly what an editorial team needs. The problem is the reading layer.
The admin screens give a month grid and a flat list, and that is it. Marketing teams end up keeping a parallel spreadsheet to track webinars against workshops, and editorial leads keep their own document to track what stage each event is in. SleekView reads the same rows and turns any column into a real kanban board.
event_category becomes a marketing board, a custom stage column becomes a pipeline, and the author field becomes a workload board. Drag and drop writes back to the row through the SleekView writer with the same capability checks the admin screen uses, so the data stays the source of truth and the parallel spreadsheets can finally go away.
Questions
Common questions about SleekView Kanban for Spiffy Calendar
Yes. SleekView treats the Spiffy table as a first-class data source and reads the schema directly. No shortcode, no transient, no scraping the calendar HTML. Custom columns you added on top of the Spiffy schema are available for grouping and display the same way native columns are.
Yes. Any column on wp_spiffy_calendar can be the group field. event_category is the default for a marketing board, and a custom stage column gives an editorial pipeline. Grouping by the author ID gives a workload board on the same dataset.
Yes. Moving a card between columns writes the new value back to the Spiffy row through the SleekView writer with the same capability checks the Manage Events screen uses. The row is updated in place, not duplicated.
SleekView surfaces a No value column at the start of the board so unsorted events are visible and assignable, instead of silently disappearing from the kanban view.
By default the board filters to upcoming events using the event_begin column, so the columns reflect the calendar going forward. You can switch the filter to include past events for archival use.
Yes. Any saved kanban view can be embedded on a frontend page through the SleekView shortcode with role-based access, so an event coordinator can read and update the board without a wp-admin login.
Yes. SleekView uses the same WordPress capabilities the Spiffy admin screens rely on, so users only see and move events they have the right to manage. Drag actions are blocked with a clear message when permission is missing.
No. The Spiffy widget renders from the same table row, so the writeback simply updates the source data. The widget reflects the new category on the next render without any extra cache invalidation step.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout