SleekView Kanban for Meta Box Views
SleekView Kanban reads your Meta Box Views records, groups them by view lifecycle or by a derived workflow state, and lets site builders drag views between Draft, In review, Active, and Archived columns to give every Meta Box view a clear lifecycle surface without writing a custom admin page just for the queue.
♾️ Lifetime License available
Why Meta Box Views sites need a kanban view
Meta Box Views is the front-end view builder for Meta Box that lets site builders render Meta Box field values inside templates using saved view definitions managed in the WordPress admin. Each view lives as a post of the mb-views post type with the field map, the template markup, and the optional CSS and JS stored as post meta keys, with values written through the standard Meta Box helpers across the site.
SleekView Kanban points at the Meta Box Views post type, lets you pick the column that holds the lifecycle state to group by (a custom lifecycle meta with values Draft, In review, Active, and Archived, the standard post_status when the workflow is publish-driven, or a derived stage built from several view fields), and renders one card per view. Each card shows the view name, the target Meta Box field group, the assignee, and the modified date so the team sees the lifecycle shape at a glance.
When a developer drags a card from In review into Active or Archived, SleekView updates the lifecycle meta on the view record, fires the Meta Box save hooks, and updates the queue counts at the top of each column. The Archived column doubles as a history view so old Meta Box views stay searchable without cluttering the Active board across the site.
Workflow
Build a Meta Box Views lifecycle board in four steps
Connect SleekView to Meta Box Views
Pick the lifecycle field for columns
Decide what shows on each card front
Enable drag-and-drop with role rules
Sample board
Sample Meta Box Views lifecycle board
Comparison
Default Meta Box Views vs SleekView Kanban
Default Meta Box Views admin
- Meta Box Views displays every view on a single flat list with the target field group as a column only.
- Lifecycle stages live in meta with no visual queue around the value's flow across the site templates.
- Bulk actions exist but cannot group views by current lifecycle stage or by assignee meta value today.
- Filtering by lifecycle is not surfaced in core admin so reviewers cannot drag between queues today.
- Site builders write custom admin pages to give Meta Box Views a lifecycle board surface for the team.
SleekView Kanban
- Group Meta Box Views records by lifecycle meta, by post_status, or by a derived lifecycle state.
- Show target Meta Box field group, assignee, lifecycle label, and modified date on the card front.
- Drag a card from In review into Active and SleekView updates the lifecycle meta and post_status safely.
-
Run one board per Meta Box field group, for example a board for
vendorand one for events. - Roles can be limited to view owners so general editors never see the lifecycle board on the site.
Features
What SleekView Kanban gives you for Meta Box Views
Lifecycle board for every Meta Box view
Every Meta Box Views record lands on the board with the lifecycle meta defining the columns and the most important view fields shown on each card. Site builders no longer write custom admin pages, and the standard Meta Box save lifecycle stays intact through every column move on the editor dashboard during the review.
Owner, field group, and modified date
Owner, target Meta Box field group, and modified date land on the card front, so a reviewer sees who owns the view and when it last changed without opening it. Meta Box save hooks fire when a card moves, so any audit plugin listening to the standard lifecycle hooks keeps running across the review session.
Drag writes back to the view record
When a card moves, SleekView updates the lifecycle meta and optionally the post_status on the view record, the same writes Meta Box does on save. The standard Meta Box save hooks fire so any custom code listening to the standard lifecycle hooks continues to run after every column change on the board.
Audience
Site builders that put it on the editor dashboard
Agency teams managing shared view libraries
Agency teams keep many Meta Box views across many client sites and need a clear lifecycle for each one. The Draft column collects new views, In review tracks views under design review, Active holds production views, and Archived doubles as searchable history without polluting the Active board on the dashboard.
Maintainers reviewing view safety
Maintainers review every view before promoting it to Active. The board makes it clear which views are still In review against the next release, and the standard Meta Box save hooks update any audit log when a view moves into Active without further plugin glue work or extra setup.
Teams archiving legacy views cleanly
Teams archive legacy views cleanly. Moving a card into Archived sets the lifecycle meta so the Active board stays clean. The Archived column doubles as searchable history across every quarter the team runs without spreadsheets tracking old view versions outside the admin set on the site at once.
The bigger picture
Why a Meta Box Views kanban turns views into a real lifecycle
Meta Box Views is where site builders go to render Meta Box field values inside templates using saved view definitions managed in the admin. The default admin still shows every view on a single flat list with the target field group as a column, which means lifecycle only lives in people's heads or in a separate spreadsheet that nobody updates after the design review meeting. A kanban view changes that shape.
The lifecycle meta becomes the columns, the most important view fields land on the cards, and the board gives every Meta Box view a real lifecycle surface without writing a custom admin page. The In review column becomes the work, the Active column doubles as the production inventory, and the Archived column makes it safe to retire old view versions without deleting them. Moving cards keeps the standard Meta Box save hooks in play, so any audit log or notification plugin stays correct after every column change.
The work feels small because each card is small, and the board makes the size of every queue honest across every site the team runs against many client projects at once.
Questions
Common questions about SleekView Kanban for Meta Box Views
Yes. Moving a card updates the lifecycle meta and optionally the post_status on the view record, the same writes Meta Box does on save. The standard Meta Box save hooks fire so any custom code listening to the standard lifecycle hooks continues to run after every column change on the board.
SleekView reads the Meta Box Views post type directly and joins meta per view. You pick the source, choose the lifecycle meta or post_status to group by, and SleekView renders one card per view with the fields you select for the card front, including the target field group, the assignee, and the modified date.
Yes. SleekView ships with role-based permissions, so view owners can have a single page that holds the lifecycle board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move views into Active without a maintainer's approval move first.
Derived states are first-class in SleekView. You can define a lifecycle state computed from several view fields, such as treating a view as In review when post_status is draft and a Review flag is present, and SleekView groups views by that derived value across the columns for the entire team.
Each board has one source so the rules stay clear, but most setups run one board per target field group, for example a Vendor field group board and an Event field group board on the same editor dashboard. Column counts at the top show waiting work at a glance for every field group.
Dragging never deletes data. It updates the lifecycle meta and optionally post_status on the view record, which is the same thing a save in the Meta Box Views editor does. Other view fields, including the template markup, the CSS, and the JS, are not touched by SleekView so the view stays exactly as saved.
Yes. Each card can show the time since the view was last modified or since the lifecycle meta was last updated, so a view stuck in In review for a month looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column to keep stale views visible.
No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the view post type and the lifecycle meta. Sites with thousands of Meta Box Views records stay responsive because heavy fields such as the template markup are only fetched for cards currently on screen.
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