SleekView Kanban for Pods
SleekView Kanban reads any Pods pick field on a custom content type and renders one card per record, grouped into columns by the option you pick. Dragging writes the new value through the Pods API, whether your pod stores values in postmeta or in a custom database table.
♾️ Lifetime License available
Why Pods content needs a status board
Pods is unusual in WordPress land because it can store data in three different places. A pod extending a post type writes to wp_postmeta, a pod extending a user writes to wp_usermeta, and an advanced content type writes to its own custom table like wp_pods_projects. Every storage path ends up flat in the admin, sorted by date or ID, with no grouping by a pick field like project_stage or asset_status.
SleekView Kanban reads pod definitions through pods_api(). Any pick field with a fixed set of options can act as the grouping axis, and the choices you defined in the pod editor become the kanban columns in the order you saved them. Card layouts pull text, number, date, file, and relationship fields and render each one with the right widget without manual setup.
Dragging a card calls pods()->save() with the new option value. Pods triggers its own pre_save and post_save hooks, so any custom validation, magic tags, or integrations continue to fire. For advanced content types stored in a custom table, the write hits the table directly through the Pods API rather than the slower meta path.
Workflow
From Pods config to live board in four steps
Connect to a Pods content type
Pick the status column to group by
Choose what shows on each card
Enable drag and drop writes
Sample board
Sample Pods asset tracker board
Comparison
Default Pods admin versus SleekView Kanban
Default Pods record list
- Pods records list flat in the admin with no grouping by pick fields
- Advanced content types render in a basic table with no status overview
- Reading a status forces a click into the edit form per record
- Bulk edit is limited and rarely covers user defined pick fields
- No drag interaction means no visual sense of pipeline shape
SleekView Kanban
-
Reads pod definitions through
pods_api(), no manual schema mapping - Works on post backed pods, user backed pods, and advanced content types
- Cards render file, relationship, date, and number fields with native widgets
-
Drag calls
pods()->save()so pre and post save hooks still fire - Falls back to read only when the user lacks the pod level capability
Features
What SleekView Kanban gives you for Pods
Every Pods storage backend
Post backed pods write through postmeta, user backed pods through usermeta, and advanced content types write straight to their dedicated table. The board talks to all three through pods_api so behavior stays consistent regardless of where the underlying data sits.
Save through the official API
Drag operations call pods->save on the new value rather than poking the database directly. Pre save and post save hooks run, magic tags refresh, and any field validation registered in the pod editor still applies to the new column value.
Filters that match your pod
Filter cards by any field in the pod through a filter bar. Text, number, date, and relationship fields all get appropriate input widgets. Numeric ranges use BETWEEN, dates use timestamp comparisons, and the filter state is saved per user per board.
Audience
Three Pods builds that need a board
Asset tracking
An Assets advanced content type with status, owner, and due date fields becomes an internal equipment board. Operators drag items between Available, Checked out, In repair, and Retired without writing custom admin screens for each transition.
Member onboarding
A user backed pod with an onboarding_step pick field renders as an onboarding pipeline. New signups land in Welcome, move to Profile complete, then Verified, then Active. Hooks on each save fire welcome emails, badge grants, and Slack alerts.
Internal request queues
Pods extending a custom post type for IT, facilities, or HR requests become a triage board. Requesters submit through a Pods form on the front end and operators move records through Open, In progress, and Resolved without learning a new tool.
The bigger picture
Why Pods deserves a first class reporting layer
Pods has always punched above its weight in the WordPress ecosystem. It lets a single plugin model relational data the way you would in Django or Rails, without writing migration files or learning a separate ORM. The trade off is that the reporting layer never quite caught up with the modeling layer.
Once a team commits to advanced content types for projects, inventory, contracts, or members, they discover that the default admin still shows everything as one flat list per content type. A kanban board fixes the gap without adding a parallel data model. The status field stays in the pod, validation and hooks stay in the pod, and the board is purely a render layer that calls pods_api like the rest of the plugin does.
Teams that adopt it usually replace half a dozen custom admin screens that existed only to give operators a way to see work grouped by stage.
Questions
Common questions about SleekView Kanban for Pods
Both. Pods exposes the same API for post backed pods and for advanced content types stored in custom tables. SleekView Kanban uses pods_api for definitions and pods()->save for writes, so it works the same way regardless of which storage backend the pod uses.
Single value pick fields with a fixed option set. Custom option lists, simple relationship fields with a closed set, and yes-no pick fields all work. Bi-directional relationship fields are excluded because they can hold many values and would put the same card in several columns.
They fire in full. The plugin calls pods->save with the new value, which triggers pre save and post save hooks in the normal order. Magic tags refresh, field validation runs, and any custom code attached to those hooks continues to work without modification.
Yes. The capability check uses the same logic the Pods admin uses for the edit form. Users who lack edit on a pod see the board in read only mode. Users with edit see drag handles and can move cards. Add new is gated by the equivalent capability for that pod.
Yes. Relationship fields render as the related record title plus an optional avatar or thumbnail. Clicking a relationship widget on a card opens the related record in the Pods editor in a new tab. The board itself only edits the grouping field and the meta on the current pod.
For post backed pods you choose which post statuses appear. Published, draft, pending, and private can all be included. For advanced content types the board reads every row by default since custom tables have no equivalent of post_status. You can add a filter on any field to mimic a status filter.
Cards load lazily per column. The plugin uses indexed queries on the storage table and avoids meta_query joins when possible. Boards stay responsive into the hundreds of thousands of rows as long as the grouping field column has an index defined in the pod schema.
Yes. Advanced content types store every field as a column on the custom table, and the Pods API writes directly to those columns when pods->save is called. The board behavior is identical to a post backed pod, but the write is faster because it avoids the wp_postmeta join.
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