SleekView Kanban for Seriously Simple Podcasting
SleekView reads the podcast custom post type Seriously Simple Podcasting creates, groups every episode by post_status, and lets your team drag episode cards between Draft, Edit, Scheduled, and Published so the underlying post updates the moment the column changes.
♾️ Lifetime License available
Why podcast episodes fit a kanban view
Seriously Simple Podcasting stores every episode as a row in the standard wp_posts table under the podcast custom post type, with audio file URL, duration, and episode number stored in wp_postmeta against keys like audio_file, duration, episode_number, and cover_image. Each episode carries a normal WordPress post_status value, which ends up being the single most useful field for tracking where any given episode is in production. The default Posts screen lists episodes in chronological order, which is fine for an archive and unhelpful when three editors need to know what is in the recording queue right now.
SleekView Kanban reads the same wp_posts rows the All Episodes screen lists. Pick post_status as the grouping field and every episode becomes a card grouped under Draft, Edit, Scheduled, or Published. Card fronts can show the episode number, the guest name from a custom field, the recorded date, the runtime, and a flag for whether audio_file meta is populated so the producer can see at a glance which episodes still need a file uploaded to the SSP audio host.
Dragging a card between columns runs the same status transition the post editor uses. The transition_post_status action fires normally, which means the SSP audio host syndication, the RSS feed rebuild, and any subscriber to ssp_episode_published all run exactly as they would after a manual save. A move to Scheduled honors the post date, and a move back to Edit safely unschedules without leaving a half-published episode in the feed.
Workflow
From the episode queue to a live production board
Connect the podcast post type
Pick post_status as the group column
Choose what each episode card shows
Enable drag-and-drop status updates
Sample board
Sample Seriously Simple Podcasting board
Comparison
Default SSP episode screen vs SleekView Kanban
Default SSP episodes list
- Chronological list of every episode with post_status as a tiny label per row
- No visual way to see whether the Edit column is bottlenecked behind a single producer
- Tracking which episodes are missing an audio_file upload means scrolling each row
- Scheduling changes require opening the post editor and using the date picker every time
- Producers need editor access and a Trello board on the side to coordinate the team
SleekView Kanban
-
Reads from the standard
wp_poststable under the SSP podcast post type -
Drag a card to Published and
transition_post_statusfires normally for RSS - Cards show episode number, guest, runtime, recorded date, and missing-file flag
- Column counts update live so editing bottlenecks surface during the production sync
-
Per-role capabilities tie writeback to
publish_postsfor producer access
Features
What SleekView Kanban gives you for Seriously Simple Podcasting
Native SSP episode model
Every column maps to a real WordPress post status registered for the SSP podcast post type. RSS feed rebuilds, audio host syndication, and Apple Podcasts pings continue to run on status transitions, so a manual move never leaves a half-published episode in the feed or skips a syndication step.
Drag-and-drop with audit trail
Each move writes a post meta entry naming the producer who dragged it, the source column, the destination column, and the timestamp. If a host pushes an episode from Scheduled back to Edit for a last-minute correction, the chain of custody stays visible to the rest of the production team.
Scheduling shortcuts per board view
Filter to the next two weeks for the producer, missing-audio episodes for the editor, and scheduled-but-not-syndicated rows for the marketing lead. Each saved view becomes a shareable URL that opens straight into the right board ahead of the weekly production standup.
Audience
Where an SSP kanban changes podcast production
Producer triage board
Producers work the Draft column left to right, dragging each episode to Edit as the raw audio arrives from the recording platform and to Scheduled once the final mix lands so the host always knows what is on deck for the week ahead.
Editor mix queue
Audio editors scope the board to the Edit column, watch the missing-file flags, and confirm the loudness pass for each episode before dragging the card to Scheduled. Episodes never publish without a final file in place.
Marketing scheduling lane
Marketing watches the Scheduled column to align social posts and newsletter mentions with each episode's publish date, then uses the Published column to confirm which episodes need amplification a week after release.
The bigger picture
Why this view matters for a podcast workflow
Podcast production is a multi-stage workflow that lives inside WordPress for distribution but rarely inside WordPress for coordination. Most shows end up with a Trello or Notion board that mirrors what is happening in WordPress and quickly drifts out of date. The producer marks an episode as ready on the side, the host marks it as published in WordPress, the editor marks it as mixed in a Google Doc, and by week three nobody agrees on what is actually in the feed.
A kanban view that reads and writes the same Seriously Simple Podcasting episode rows as the WordPress editor keeps the production team and the source of truth aligned. Draft, Edit, Scheduled, and Published all live in one place. Missing audio files surface before the publish date, not after a listener complaint.
The feed and the team's mental model stop drifting apart for the rest of the season.
Questions
Common questions about SleekView Kanban for Seriously Simple Podcasting
Live. SleekView queries the same wp_posts rows the All Episodes screen reads from. Filters apply at the SQL level, so a board scoped to this season reflects only episodes tagged into that season's taxonomy term, not yesterday's export of every episode the show has ever recorded.
Yes. The drag fires wp_transition_post_status with the new status, which is the same path the post editor uses. RSS feed rebuilds, audio host syndication, and any custom hook listening for ssp_episode_published all run as normal, including pings to Apple Podcasts if configured.
Yes. Group by a custom production_stage meta field instead of post_status and the board renders one column per value. Teams that track Recorded, Mixed, Mastered, and Shipped as separate phases find the granularity useful without disturbing the underlying WordPress post status.
Yes. Every move runs through current_user_can('publish_posts') or current_user_can('edit_posts') as appropriate before the status transition hits the database. An editor without publish rights can drag for personal sorting, but the change does not persist and a toast notification explains why.
Filters are applied at the database query level rather than in JavaScript. A typical board scopes to the current season's taxonomy term or to in-production status values only, so the rendered card count stays small. Older episodes remain queryable in archive views without slowing the live board.
Yes. The audio_file meta key SSP writes when a file is attached is exposed as a card field. Episodes without that meta value can show a missing-file flag or even appear in red so the producer can act on the gap before the publish date arrives.
Yes. Castos hosting and local-file SSP installs both write the same audio_file meta key, just with different URLs. The card mapping treats both identically, so a board can include episodes hosted on Castos, on the WordPress media library, and on a third-party CDN without separate configurations.
Yes. Every drag writes a post meta entry naming the user, the source column, the destination column, and the timestamp. The entry uses standard WordPress meta storage, so audits, exports, and downstream automations can read it without a separate event log or third-party service.
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