SleekView Kanban for JetEngine
SleekView Kanban reads any JetEngine select meta field on a registered post type or custom content type and renders one card per record, grouped into columns by the value you pick. Dragging a card updates the meta and refreshes any JetEngine listing that depends on it.
♾️ Lifetime License available
Why JetEngine apps need a kanban view
JetEngine is the most extensive WordPress plugin for building data applications inside the Crocoblock stack. It registers post types, custom content types stored in their own tables, taxonomies, and meta boxes. The default WordPress admin lists every one of these as a flat table with no grouping by a JetEngine select field like jet_project_stage or jet_lead_status. JetEngine Listings render the same data on the front end but rarely sit inside the admin where operators work.
SleekView Kanban reads JetEngine meta box definitions and CCT schemas through the official JetEngine API. Any select or radio meta field with a fixed option list can be the grouping axis, and the options you defined in the meta box editor become the four kanban columns in the same order. Cards render JetEngine text, number, date, media, and relations fields with the right widget for each type.
Dragging a card writes the new meta value through update_post_meta or the CCT save API, and JetEngine listings, dynamic widgets, and Bricks queries that depend on the field re-render correctly. JetEngine Access settings still gate writes, so users without the right role see the board in read only mode and the drag handles stay hidden.
Workflow
From JetEngine schema to live board in four steps
Connect to a JetEngine post type or CCT
Pick the status column to group by
Choose what shows on each card
Enable drag and drop writes
Sample board
Sample JetEngine lead pipeline board
Comparison
Default JetEngine admin versus SleekView Kanban
Default JetEngine record list
- JetEngine CPTs and CCTs list as flat tables with no select grouping
- Reading a record status requires opening the JetEngine meta box
- Bulk edit rarely covers JetEngine meta box select or radio fields
- Listings live on the front end, not where operators do daily triage
- No drag interaction, so pipeline shape is invisible at a glance
SleekView Kanban
- Reads JetEngine meta box and CCT schemas through the JetEngine API
- Works on registered post types and on standalone CCT tables
- Cards display media, relations, date, and number fields natively
-
Drag fires
update_post_metaor the CCT save API, listings refresh - Honors JetEngine Access roles for read and write per content type
Features
What SleekView Kanban gives you for JetEngine
Post types and CCTs both
JetEngine stores some content in standard postmeta and other content in dedicated CCT tables. SleekView Kanban handles both, reading the right schema through the JetEngine API and writing through the matching save path so behavior stays consistent for operators.
Listings stay in sync
When a card moves, the underlying meta value changes through the official write path. Any JetEngine Listing, dynamic widget, or Bricks query that filters by the status field re-renders on the next request the same way it would after a manual save.
JetEngine Access aware
If JetEngine restricts editing a content type to a custom role, the board enforces the same rule. Authorized users see drag handles. Other users see the same layout in read only mode with a tooltip explaining which role is required to make changes.
Audience
Three JetEngine builds that need a board
Sales pipelines
A Leads CCT with status, owner, and deal value fields becomes a CRM-style board. Dragging a lead from Qualified to Proposal updates the CCT row, refreshes the related listing on the dashboard, and triggers any JetEngine event that depends on the status change.
Editorial workflows
Article post types with a JetEngine workflow_state meta field render as a publishing board. Drafts move through Outline, Writing, Review, and Scheduled stages. JetEngine Access keeps junior editors from skipping the review column.
Service ticket queues
Ticket CPTs with a JetEngine ticket_status select become a triage board. Front end submission forms create tickets, operators drag them across Open, In progress, Waiting on customer, and Resolved, and listings on the customer portal stay in sync.
The bigger picture
Why JetEngine apps deserve a board
JetEngine is closer to a low code application framework than to a typical WordPress plugin. Teams use it to build CRMs, real estate portals, directories, and entire intranets. The plugin gives you everything you need to model the data and to render it on the public site through listings and dynamic widgets, but it deliberately leaves the operator admin alone.
That choice keeps JetEngine compatible with the rest of the WordPress admin, and it also means that anyone building serious internal workflows ends up writing custom admin screens just to see records grouped by stage. A kanban board removes that work. The status field stays in JetEngine, the schema stays in JetEngine, and the board is a thin render layer over the same data the rest of the application already uses.
The result is that operators stop needing custom admin code and start using a consistent view across every JetEngine content type.
Questions
Common questions about SleekView Kanban for JetEngine
Yes. The plugin detects whether the chosen content type is a registered post type or a JetEngine custom content type and uses the right read and write path for each. CCTs read from their dedicated table and write through the JetEngine CCT save API rather than through postmeta.
Select, radio, and checkbox single value meta fields with a fixed option list. Multi value checkboxes are not eligible because a single record could land in several columns. The board uses the options exactly as you saved them in the JetEngine meta box editor.
Yes. Dragging a card writes the new meta value through the official save path, so any listing or dynamic widget that queries by that field rebuilds on the next page load. Cache plugins still apply, so cached pages refresh on their own schedule unless you flush the cache.
It enforces them. The capability check uses the same logic the JetEngine admin uses for the meta box save action. Users who can edit see drag handles and can move cards. Users who cannot see a read only board with a tooltip explaining the missing role.
Yes. Relations render as the related record title with an optional thumbnail. Clicking the widget opens the related record in the JetEngine editor in a new tab. The board itself only edits the grouping field on the current record, not the related one.
Filter macros are available in the filter bar. You can pre filter the board by any JetEngine meta field or by a query variable, then apply additional filters on the rendered board. Saved board filters persist per user so each operator returns to their working view.
They fire the same way they would on a manual save. The plugin calls the standard save action, which triggers the JetEngine event manager. Notifications, integrations, and any custom event handlers that listen for the meta change continue to run without changes.
Columns stream cards lazily, so the row count limit is whatever the storage backend can return per query. Boards stay responsive into the hundreds of thousands of records as long as the grouping field column on the CCT or the meta key in postmeta is indexed.
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