SleekView Kanban for Carbon Fields Pro
SleekView Kanban reads your Carbon Fields Pro records, groups them by any Carbon Select or derived review state, and lets developers drag records between Draft, In progress, Review, and Published columns to give every Carbon container a real review surface without writing a custom admin page just for the queue.
♾️ Lifetime License available
Why Carbon Fields Pro sites need a kanban view
Carbon Fields Pro is a developer-first field framework that lets you register containers in code and attach fields to posts, terms, users, options, or comments. Records live in the standard WordPress tables, and field values save through the Carbon Fields API into the matching meta tables, so the data shape is identical to standard WordPress meta but the definitions live in code rather than in a UI.
SleekView Kanban points at the post type backed by a Carbon container, lets you pick the column that holds the review state to group by (a Carbon Select field, a derived review_state built from several Carbon fields, or the standard post_status when the workflow is publish-driven), and renders one card per record. Each card shows the record title, a Carbon User field for the assignee, a Carbon Date field for the due date, a Carbon Association field for the related post, and the modified timestamp.
When a developer drags a card from In progress into Review or Published, SleekView writes the new value through the Carbon Fields API carbon_set_post_meta helper, fires the carbon_fields_post_meta_container_saved hooks, and updates the queue counts at the top of each column. The Published column doubles as a review history view so old Carbon records stay searchable without cluttering the Draft board on the dashboard.
Workflow
Build a Carbon Fields Pro review board in four steps
Connect SleekView to Carbon Fields Pro
Pick the review state field for columns
Decide what shows on each card front
Enable drag-and-drop with role rules
Sample board
Sample Carbon Fields Pro review board
Comparison
Default Carbon Fields Pro vs SleekView Kanban
Default WordPress admin
- Carbon-backed custom post types display as flat lists with Carbon field values shown only as columns.
- Review stages live inside a Carbon Select field with no visual queue around the value's lifecycle.
- Bulk actions exist but cannot group records by current review stage or by Carbon user assignments.
- Filtering by stage requires custom code so reviewers cannot drag a record between queues today.
- Site builders write custom admin pages to give Carbon-backed records a board-like review surface.
SleekView Kanban
- Group Carbon Fields Pro records by any Carbon Select, Radio, or Set field on the registered container.
- Show Carbon User, Date, Association, and Select fields on the card front for review context at a glance.
-
Drag a card from In progress into Review and SleekView calls
carbon_set_post_metasafely. - Run one board for each Carbon-backed post type and switch between them on the same dashboard cleanly.
- Roles can be limited to record owners so general users never see the Carbon review board on the site.
Features
What SleekView Kanban gives you for Carbon Fields Pro
Review surface for every Carbon model
Any Carbon-backed custom post type becomes a review board, with the Carbon Select field defining the columns and the most important Carbon fields shown on each card. Site builders no longer write custom admin pages, and the standard Carbon save lifecycle stays intact through every column move on the dashboard.
Owners, dates, and associations on the card
Carbon User, Date, and Association fields land directly on the card front, so a reviewer sees ownership, due date, and the related post without opening the record. Carbon save hooks fire when a card moves, so any notification or audit plugin listening to the Carbon container saved hook keeps running cleanly.
Drag writes back through Carbon Fields API
When a card moves, SleekView calls carbon_set_post_meta for the chosen Carbon Select field, which is the same helper Carbon Fields uses on save. The Carbon container saved hook fires so any custom code listening to the standard Carbon hooks continues to run after every column change on the board.
Audience
Developer teams that put it on the editor dashboard
Developer teams running editorial reviews
Developer teams that model content in code with Carbon Fields keep the workflow code-driven too. The board makes it clear which records are in Draft, In progress, Review, or Published, and the Carbon container saved hook updates any notification plugin when a record moves into Published without extra glue.
Marketing teams reviewing vendor profiles
Marketing teams model vendor profiles as Carbon-backed records with Date fields. The board makes it clear which profiles are still in Draft against the next campaign, and the Carbon container saved hook updates audit logs when a profile moves into Published without any further plugin glue work or setup.
Knowledge teams reviewing KB articles
Knowledge teams model KB articles as Carbon-backed records. The In progress column tracks live editorial work, Review captures the second pass, and Published doubles as the KB inventory across every quarter the knowledge team runs without spreadsheets tracking which articles already landed.
The bigger picture
Why a Carbon kanban turns code-driven models into real reviews
Carbon Fields Pro is the framework developer teams choose when they want field definitions to live in code rather than in a UI. The default WordPress admin still shows Carbon-backed records as flat lists with extra columns, which means review stage only lives in people's heads or in a separate spreadsheet that nobody updates after the review meeting. A kanban view changes that shape.
Any Carbon Select field becomes the columns, the most important Carbon fields land on the cards, and the board gives every model a real review surface without writing a custom admin page. The In progress column becomes the work, the Published column doubles as the searchable inventory, and the Review column makes the second-pass step visible across the team. Moving cards keeps the Carbon Fields API in play, so the Carbon container saved hook 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 every queue honest across every model the dev team manages in code today.
Questions
Common questions about SleekView Kanban for Carbon Fields Pro
Yes. Moving a card calls carbon_set_post_meta for the chosen Carbon Select field, the same helper Carbon Fields uses on save, so the Carbon container saved hook fires and any custom code listening to the standard Carbon hooks continues to run after every column change on the review board for the team.
SleekView reads the post type that holds the Carbon container and joins Carbon meta directly. You pick the source, choose the Carbon Select field to group by, and SleekView renders one card per record with the Carbon fields you select for the card front, including Association, Date, and User fields.
Yes. SleekView ships with role-based permissions, so record owners can have a single page that holds the review board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move records into Published without a manager's approval move first.
Derived states are first-class in SleekView. You can define a review_state computed from several Carbon fields, such as treating a record as Review when an approval flag is false and a stage Select equals review, and SleekView groups records by that derived value across the columns for the dev team.
Each board has one source so the rules stay clear, but most setups run one board per Carbon-backed post type and switch between them on the same editor dashboard. Column counts at the top of each show waiting work at a glance for every post type the dev team manages across the site.
Dragging never deletes data. It calls carbon_set_post_meta for the chosen Carbon Select field, which is the same thing a save in the Carbon-backed editor does. Other Carbon fields are not touched by SleekView, so all field values, including Association, Date, and Complex field rows remain exactly as saved.
Yes. Each card can show the time since the post was last modified or since the Carbon Select field was last updated, so a record stuck in In progress for a week looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column to keep stale work visible.
No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the post type and the Carbon Select meta key. Sites with hundreds of thousands of Carbon-backed records stay responsive because heavy Carbon fields such as Complex 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