SleekView Kanban for Simple Calendar
Simple Calendar pulls Google Calendar events into the gce_feed custom post type and caches occurrences with summary, start, end, location, and organiser. SleekView reads the cached events, groups by source calendar or event status, and shows one card per occurrence.
♾️ Lifetime License available
Read your Google Calendar feeds as a real board
Simple Calendar connects to Google Calendar and stores each feed as a gce_feed custom post type with the calendar ID, the API credentials, and the display options. Fetched events are cached in transients keyed per feed with the summary, start time, end time, location, organiser, and Google event status (confirmed, tentative, or cancelled). The frontend renders the feed as a grid or list. There is no admin board view of the underlying events.
SleekView reads the gce_feed posts and the cached event payloads together as a single data source. Each row is one Google occurrence with the feed name, the calendar ID, the start time, the location, the organiser, and the Google status. Flip the view to Kanban and pick the source feed as the group column for a multi-team board, or pick the Google event status to separate confirmed events from tentative and cancelled ones.
Drag and drop write-back is opt-in because the source of truth lives in Google. With write-back off, the kanban is a read-only board on top of the cached data, perfect for an at-a-glance ops view that refreshes when Simple Calendar refreshes its feed transient. With write-back on, SleekView updates the event in Google through the same API credentials Simple Calendar already stores on the feed post.
Workflow
From gce_feed cached events to a kanban in four steps
Connect SleekView to Simple Calendar feeds
Pick the group column
Choose what shows on each card
Enable drag and drop writeback (optional)
Sample board
Sample Simple Calendar feeds board
Comparison
Default Simple Calendar grid vs SleekView Kanban
Default Simple Calendar
- Simple Calendar renders a grid or list per feed with no board mode in admin
- Multiple feeds stay visually separate even when teams need to read them together
- Google event status (confirmed, tentative, cancelled) is not surfaced as a grouping
- Organiser and location are present in the cached payload but not in the admin list
- No saved view per role for ops, marketing, or community
SleekView Kanban
-
Read cached Google occurrences from the
gce_feedpost type as kanban cards -
Group by source feed for a team board or by
statusfor confirmed and tentative split - Card fronts show summary, start time, location, and organiser
- Optional drag and drop writeback through the same Google API credentials Simple Calendar stores
- Read-only boards are safe by default since Google stays the source of truth
Features
What SleekView Kanban gives you for Simple Calendar
Google fields on the card front
Summary, start time, end time, location, organiser, and status from the cached Google payload appear on the card front so the board reads as a working schedule and not an abstract list.
Group by feed or by status
Source feed gives a multi-team board, the Google event status gives a confirmed and tentative split, and grouping by organiser shows workload per person on the same dataset.
Read-only by default
Google is the source of truth, so write-back is opt-in. The default board is a read-only view on top of the cached data with no risk of accidentally rewriting your Google calendar.
Audience
Who runs a Simple Calendar board with SleekView
Operations teams
Group multiple Google feeds in one board to see what every team is running this week without flipping between calendars.
Event coordinators
Watch the Tentative column to see which events still need a confirmed response from speakers, venues, or partners.
Community managers
Use the source feed grouping to keep external community events visually separate from internal team calendars on one screen.
The bigger picture
Google has the data, WordPress should have the board
Most teams already run their calendars in Google. Simple Calendar pulls those feeds into WordPress and renders them on the frontend, which is exactly what a public website needs. The gap is internal.
An ops team wants to see across feeds at a glance, an event coordinator wants tentative events visible, and a community manager wants external and internal feeds visually separated. The Simple Calendar admin does not provide any of that. SleekView reads the same cached Google payloads, groups them by source feed or by Google event status, and lets the team work on a real board while Google stays the source of truth.
With write-back off the board is safe by default, with write-back on it uses the same credentials Simple Calendar already stores on the gce_feed row. Either way the team finally has a board for the calendar they were already running.
Questions
Common questions about SleekView Kanban for Simple Calendar
No. Write-back is off by default because Google is the source of truth and Simple Calendar is primarily a reader. The default board is a read-only view of the cached events, which is safe to share widely. Write-back is an explicit opt-in per board.
SleekView reads the gce_feed posts and the cached event payloads Simple Calendar stores per feed in transients. Each cached occurrence becomes a row with summary, start, end, location, organiser, status, and feed name available for grouping and display.
Only if write-back is enabled. With write-back on, SleekView updates the event in Google through the API credentials Simple Calendar already stores on the gce_feed post, using scopes Simple Calendar uses for read plus the write scope you grant during opt-in.
The board reads the same cached event data Simple Calendar renders on the frontend, so freshness matches the Simple Calendar refresh interval set per feed. Forcing a refresh on a feed updates both the frontend and the board on the next load.
Yes. The data source can include any number of gce_feed posts and SleekView normalises every cached event into the same row shape. Grouping by source feed then gives a multi-team board on a single screen.
Yes. The board filter accepts the Google event status field, so a board can be scoped to confirmed and tentative only, or include cancelled as a fourth column for audit and cleanup work.
Yes. SleekView only reads gce_feed posts the current user can access through the standard WordPress capability map, so users only see feeds they would already see in the Simple Calendar admin.
Yes. Any saved kanban view can be embedded on a frontend page through the SleekView shortcode with role-based access, so a team can read the board without a wp-admin login. The same role scoping that controls feed access applies on the frontend embed.
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