SleekView Kanban for Carbon Fields
SleekView Kanban reads any Carbon Fields select or radio container field on a post type and renders one card per post, grouped into columns by the value you pick. Dragging a card writes the new value through the Carbon Fields API and fires the same actions as a manual save.
♾️ Lifetime License available
Why Carbon Fields posts need a board
Carbon Fields is the developer-first metadata layer for WordPress. Fields are declared in PHP through Container and Field classes, and values land in wp_postmeta under your chosen prefix, usually _ for hidden meta. The default WordPress edit screen still presents posts as a flat table sorted by date, with no native way to group records by a Carbon Fields select like _project_stage or _workflow_status.
SleekView Kanban introspects Carbon Fields containers through the plugin's own field repository. Any select or radio field declared on a post container can act as the grouping axis, and the options you registered in PHP become the kanban columns in registration order. Card layouts read text, image, association, and date fields and render each one with a widget that matches its declared type.
Dragging a card calls carbon_set_post_meta() with the new option value, so the Carbon Fields save lifecycle runs exactly as it would on a manual save. Any carbon_fields_post_meta_container_saved actions you registered continue to fire, validation closures still execute, and association fields update relationships through the official API rather than direct database writes.
Workflow
From PHP container to live board in four steps
Connect to your Carbon Fields container
Pick the status column to group by
Choose what shows on each card
Enable drag and drop writes
Sample board
Sample Carbon Fields content audit board
Comparison
Default Carbon Fields admin versus SleekView Kanban
Default WordPress post list
- Carbon Fields values are hidden meta and never appear in WP_List_Table
- Status reads require opening the post editor for every record
- Bulk edit cannot reach Carbon Fields select or radio values
- Repeater and association values are invisible in the default admin
- No drag interaction means no visual signal of pipeline depth
SleekView Kanban
- Reads Carbon Fields containers through the plugin's official repository
- Cards render image, association, date, and rich text fields natively
-
Drag calls
carbon_set_post_meta()so container actions fire - Respects capability arguments declared on each container
- Falls back to read only when the user lacks the required capability
Features
What SleekView Kanban gives you for Carbon Fields
PHP-first metadata, GUI-first reads
Containers stay declared in code, the way Carbon Fields was designed to be used. The board is a pure render layer over the same field repository, so there is no parallel admin config to keep in sync and no shadow registry of fields stored in the database.
Save through the official API
Each card move calls carbon_set_post_meta on the new value. The container save lifecycle runs from there, so registered actions, validation closures, and association field side effects all fire as if a developer had submitted the post editor manually.
Filter by any container field
Filters target text, number, taxonomy, date, and association fields through a unified filter bar. Server side meta_query keeps boards fast on large post types, and saved filter state persists per user so each operator returns to their working view.
Audience
Three Carbon Fields workflows that need a board
Content audit pipelines
Long lived posts with an audit_status select field become a content quality board. Editors see Not started, In progress, Needs review, and Published columns and drag entries through the audit cycle without leaving the admin for a spreadsheet.
Project trackers
A Projects custom post type with a project_stage select and owner association becomes a development board. Cards show the project name, owner avatar, and due date, and dragging a project through the columns updates Carbon Fields meta cleanly.
Editorial pipelines
Standard posts with a Carbon Fields workflow_state field render as a newsroom board. Drafts move through Outline, Writing, Review, and Scheduled columns. Container save actions fire on each move so external workflow tools stay informed.
The bigger picture
Why Carbon Fields needs a board, not an admin column
Carbon Fields was built for developers who would rather declare their schema in code than click through an admin form builder. That philosophy is exactly why the plugin tends to power large editorial and product sites. It also means that operators on those sites never see Carbon Fields values in the default WordPress admin, because everything Carbon Fields writes is hidden meta by convention.
The usual workaround is to add manage_posts_columns and manage_posts_custom_column filters for every field worth surfacing, which works for one or two fields and falls apart for ten. A kanban board solves the underlying problem. Status fields stay declared in PHP, the container save lifecycle continues to be the single write path, and the board reads through the same field repository the rest of Carbon Fields uses.
Teams stop maintaining custom admin columns and start using a consistent view across every content type that has a status worth tracking.
Questions
Common questions about SleekView Kanban for Carbon Fields
Both. Carbon Fields registers containers on its boot action regardless of where the file lives, and the plugin reads from the same repository. As long as your container is declared by the time the board renders, its fields appear on the board without any extra setup.
Select and radio fields with a fixed set_options or add_options array. Multi select and checkbox fields are excluded because a single post could end up in several columns at once. The board uses the option keys exactly as you registered them in PHP.
They fire as if a developer had saved the container manually. The plugin calls carbon_set_post_meta on the new option value and the Carbon Fields lifecycle takes over from there. carbon_fields_post_meta_container_saved actions and field level validation closures both continue to run.
Yes. If you declared a capability on Container::make through where or set_priority, the board enforces the same rule. Users with the capability see drag handles and full write access. Users without it see the same layout with read only cards.
Yes. Association fields render the linked entity title and an optional thumbnail. Clicking the widget opens the linked record in its native editor. The board itself only edits the grouping field on the current post, not the associated record.
Yes. Carbon Fields blocks store their values in postmeta the same way containers do. The board reads those values through the official repository and writes through carbon_set_post_meta, so blocks rendered through render_callback stay correct after a card move.
Top level repeater rows can render as a count or as the first row preview. Complex fields render their primary visible subfield. Grouping by a value inside a repeater is not supported because the same post can hold many rows with different status values.
Columns stream cards lazily, so the limit is whatever a WP_Query call can return for the post type. Boards stay responsive into the hundreds of thousands of posts as long as the meta key on the grouping field has an index on meta_value or meta_value_num.
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