SleekView Kanban for Meta Box
SleekView Kanban reads your Meta Box field values stored in post meta on any custom post type, groups records by any Meta Box field you mark as the status column, and lets site builders drag records between Open, In progress, In review, and Done columns to give every project, vendor, or product record a real workflow surface without coding a custom Meta Box admin page.
♾️ Lifetime License available
Why Meta Box sites need a kanban view
Meta Box stores field values as post meta on standard posts, custom post types, taxonomy terms, or users, with each field key registered via the Meta Box field config. Site builders use Meta Box to model vendors, products, projects, and dozens of other entity types, but the default admin shows custom post types as flat lists with extra Meta Box columns added through field display options.
SleekView Kanban points at the post type, lets you pick the column that holds the workflow state to group by (any Meta Box field with a finite list of values like a Select or Radio, or a derived workflow_state calculated from several Meta Box fields), and renders one card per record. Each card shows the record title, the most important Meta Box fields like a User Picker for the owner, a Date Picker for the deadline, and Text or Select fields for context.
When a user drags a card from In progress into In review or Done, SleekView writes the new value through the Meta Box rwmb_set_meta helper or wp_update_post for the post itself, fires the standard hooks, and removes the card from the queue. Bulk actions and the standard Meta Box admin continue to work, but day-to-day record review finally has a queue rather than a list.
Workflow
Build a Meta Box workflow board in four steps
Connect SleekView to Meta Box
Pick the status field
Decide what shows on each card
Enable drag-and-drop reviewing
Sample board
Sample Meta Box custom record board
Comparison
Default Meta Box vs SleekView Kanban
Default Meta Box admin
- Meta Box custom post types display as flat lists with field values added as admin columns only.
- Workflow stages live inside a Meta Box Select field with no visual queue around the value's lifecycle.
- Bulk actions exist but cannot group records by current workflow stage or by Meta Box assignments.
- Site builders write custom admin pages just to give Meta Box records a board-like review surface.
- Notifications on record movement need extra code because the default admin only saves on submit.
SleekView Kanban
- Group Meta Box-backed records by any Select, Radio, or Button Group field with a finite value list.
- Show Meta Box User Picker, Date Picker, and Text fields on the card front to give context fast.
-
Drag a card from In progress into Done and SleekView calls
rwmb_set_metasafely. -
Card fronts can show derived
workflow_statevalues built from several Meta Box fields. - Roles can be limited to record owners so general users never see the workflow board surface.
Features
What SleekView Kanban gives you for Meta Box
Workflow for every Meta Box model
Any Meta Box-backed custom post type becomes a workflow board, with the Meta Box status field defining the columns and the most important Meta Box fields shown on each card. Site builders no longer write custom admin pages, and the standard Meta Box save lifecycle stays intact through every move.
Owners and dates on the card
Meta Box User Picker and Date Picker fields land directly on the card front, so a reviewer can see ownership and the next due date without opening the record. Meta Box save hooks fire when a card moves, so any notification plugin listening to rwmb_set_meta for the status key keeps running normally.
Drag writes back through rwmb_set_meta
When a card moves, SleekView calls rwmb_set_meta for the chosen Meta Box status field, which is the same function Meta Box uses on save. Meta Box save hooks and any custom code listening to the standard hooks continue to fire, so the rest of the Meta Box lifecycle keeps running through the move.
Audience
Site builders that put it on the editor dashboard
Agency teams with project records
Agency teams that model projects with Meta Box use the board for the weekly project review. Cards show owner, due date, and the project category, and the standard Meta Box save hooks keep any notification plugin running so the team is alerted when a project moves into review.
Product teams with custom catalog records
Product teams model SKUs or pricing tiers as Meta Box-backed custom post types. The In review column doubles as the launch readiness queue, and the Done column gives the team a clear record of which products shipped each week without leaving the SleekView kanban board surface.
Operations teams with task records
Operations teams model recurring tasks as Meta Box records. The Open column captures new tickets, the In progress column tracks active work, and the Done column doubles as an audit trail across every quarter the ops team runs the recurring program without manual log entries.
The bigger picture
Why a Meta Box kanban turns models into real workflows
Meta Box is the WordPress site builder's modeling kit. Teams use it to model the parts of a business that WordPress does not model out of the box, but the default admin still shows everything as a flat list of posts with extra columns, which means workflow lives only in people's heads. A kanban view changes that shape.
Any Meta Box status field becomes the columns, the most important Meta Box fields land on the cards, and the board gives every model a real workflow surface without writing a custom admin page. The In progress column becomes the work, the Done column doubles as an audit trail, and the In review column gives reviewers a clear lane. Moving cards keeps rwmb_set_meta in play, so Meta Box save hooks, integrations with MB Frontend Submission, and any audit or notification plugin stay correct after every move.
The work feels small because each card is small, and the board makes the size of the queue honest across every model the site builds.
Questions
Common questions about SleekView Kanban for Meta Box
Yes. Moving a card calls rwmb_set_meta for the chosen Meta Box status field, the same function Meta Box uses on save, so Meta Box save hooks and any custom code listening to rwmb_set_meta or to the standard WordPress save hooks continue to fire without any extra plugin glue or workarounds.
SleekView reads the post type and joins Meta Box field meta directly. You pick the post type as the source, choose the Meta Box status field to group by, and SleekView renders one card per post with the Meta Box fields you select for the card front, including User Picker, Date Picker, Text, Select, and Switch.
Yes. SleekView ships with role-based permissions, so record owners can have a single page that holds the workflow board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move records into Done without a manager's approval move.
Derived states are first-class in SleekView. You can define a workflow_state computed from several Meta Box fields, such as treating a record as In review when an approval Switch is on and a stage Select equals ready, and SleekView groups records by that derived value across the configured columns.
Each board has one source post type so rules stay clear, but Relationships can populate card meta and Group field repeats can appear as numeric badges on cards. For workflows that focus on Group rows themselves, a related post-per-row pattern works well alongside the standard SleekView Kanban setup.
Dragging never deletes data. It calls rwmb_set_meta for the chosen Meta Box status field, which is the same thing a save in the Meta Box editor does. Other Meta Box fields are not touched by SleekView, so all field values, including Group rows and Relationship links, remain exactly as the editor saved them.
Yes. Each card can show the time since the post was last modified or since the Meta Box status field was last updated, so a record stuck in In review for a week looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column for stale work.
No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the post type and Meta Box status meta. Sites with hundreds of thousands of Meta Box records stay responsive because heavy fields are only fetched for cards currently on screen during a review session.
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