SleekView for Kadence: CPTs and Kadence Blocks meta as tables
Kadence's header builder and block library are excellent for rendering. SleekView handles the other half — surfacing the post types Kadence Blocks Pro and your child theme register as sortable, filterable, inline-editable admin tables.
♾️ Lifetime License available
Kadence builds the front end — SleekView builds the admin to match
Kadence's strength is the front end: header builder, block library, dynamic block content, the Kadence Blocks Pro post-loop and post-grid blocks that read meta and ACF fields at render time. The admin side stays at WordPress defaults. List a portfolio CPT registered through Kadence Cloud, a team CPT from a starter, or a service CPT with ACF fields, and you get title, author, and date — anything else lives behind a click-through to the editor.
SleekView reads wp_posts joined to wp_postmeta, the same data Kadence Blocks Pro's dynamic content resolves at render time. Pick the post type, pick the meta keys (the picker shows what's actually present on the install), and you have a column set that mirrors the block-loop columns your front end shows. ACF field groups, Meta Box fields, and Kadence Blocks Pro's own meta connectors all surface through the same picker.
Inline edits route through wp_update_post and update_post_meta. Kadence's customizer remains untouched. Header-builder configurations stay where they are. Any save_post handler your child theme registered, plus ACF and Meta Box save hooks, fire identically to a manual save. Bulk-update launch dates across the portfolio CPT, flip a batch of testimonials from pending to published, correct a tier value on thirty service pages — every filter that would have run still runs.
Workflow
How SleekView reads your Kadence install's data
Pick the post type
Compose the column set
Save and scope the view
Edit inline and ship
wp_update_post and update_post_meta so Kadence Blocks Pro dynamic content and ACF hooks stay accurate.
Sample columns
A typical Kadence project-portfolio view
wp_posts joined to wp_postmeta, so portfolio, team, and case-study CPTs registered alongside Kadence work without configuration changes.
wp_posts + wp_postmeta (any CPT registered alongside Kadence)
| Project | Client | Type | Featured? | Launched | Status |
|---|---|---|---|---|---|
| Tideline rebrand | Tideline Resorts | Brand identity | Yes | Mar 12 | Published |
| Quill Books shop | Quill Books | WooCommerce | No | Mar 28 | Published |
| Solace Yoga app site | Solace Yoga | Marketing site | Yes | Apr 09 | Published |
| Halberd refresh | Halberd Legal | Web design | No | — | Draft |
| Mariner Coffee site | Mariner Coffee Co | Brand identity | No | — | Draft |
Comparison
Default WP admin list vs SleekView on Kadence
Default WP admin list
- List shows title, author, date — Kadence Blocks Pro meta hidden behind each post
- Kadence's customizer focuses on rendering, not list-table customization
- Filters limited to status, taxonomy, and date for most CPTs
- Header builder excellent — admin row management still per-post
- No saved column sets per role
SleekView
-
Reads
wp_posts+wp_postmetafor any CPT on a Kadence install - Inline-edit ACF, Meta Box, and Kadence Blocks meta in the row
- Picker lists meta keys actually present — no field-slug guesswork
- Save filtered views per role (designer, editor, account lead)
- Switch between table, kanban, and feedback-board views
Features
What SleekView gives you for Kadence theme
Column sets that mirror your block loops
If a Kadence Blocks Pro post-grid renders projects with client, type, and launch date, build a SleekView with the same fields as columns. The admin matches the front-end fidelity, so editorial review happens at the level the rendered output expects.
Inline edits route through WordPress core
Updates go through wp_update_post and update_post_meta. Kadence Blocks Pro dynamic content stays accurate, ACF save filters fire, and any save_post handler from the child theme runs identically to a manual save.
Compose filters across taxonomies and meta
Filter by project type, featured flag, launched date range, and any combination of meta values. Save the filter as a named view ("Featured projects launched this quarter") and reuse it across the team.
Audience
Who uses SleekView on Kadence sites
Agencies on Kadence Cloud
Kadence Cloud starter templates ship CPTs for portfolio, team, and testimonials. SleekView gives the admin a portfolio table with client, type, and featured-flag columns — designers update visuals, account managers scan the live list without per-post clicks.
Stores using Kadence + WooCommerce
Kadence is a popular WooCommerce theme. SleekView surfaces product post types alongside any CPT the store adds (lookbooks, brand pages, FAQ entries) so operations sees the whole content stack in one place.
Publishers and content sites
Kadence Blocks Pro post-grid is a common pattern for editorial sites. SleekView lists articles with author, taxonomy, and meta columns so editorial review happens at the same fidelity the front end shows.
The bigger picture
Why Kadence sites need an admin layer that matches the front-end builder
Kadence has invested heavily in front-end tools — header builder, block library, dynamic content, Kadence Cloud starters — and the result is one of the cleanest renderings available for any post type you throw at it. The admin layer hasn't moved. Register a portfolio CPT through a Kadence Cloud starter, attach ACF fields for client and project type, build a Kadence Blocks Pro post-grid that surfaces those fields on the front end, and you've solved the rendering side.
Now look at the admin: title, author, date, click into each post for everything else. The asymmetry compounds with site size. A studio with eighty case studies, a publisher with two hundred articles, an agency with a dozen Kadence Cloud sites — all hit the same wall.
SleekView turns the admin into a workspace that matches the rendering. The same meta keys Kadence Blocks Pro renders become columns. Designers update visuals from the row, account managers filter by featured flag, editorial reviews stay at front-end fidelity instead of dropping back to title-and-date.
Kadence keeps rendering. SleekView gives the back end the row-level workspace its data deserves.
Questions
Common questions about SleekView for Kadence theme
No. Kadence's customizer, header builder, footer builder, and theme settings stay exactly where they are. SleekView is a separate admin surface for the data inside your CPTs and their meta. Kadence keeps rendering, SleekView gives the back end a row-level workspace.
Yes. Kadence Blocks Pro dynamic content reads from postmeta and ACF fields at render time. SleekView reads the same source for the admin table view. They're complementary: Blocks Pro renders meta on the front end, SleekView surfaces it in the admin for review and bulk updates.
No. SleekView reads the database, not theme files. Whether you run Kadence parent-only, a Kadence Cloud starter, or a custom child theme, the data path is the same — wp_posts and wp_postmeta — and SleekView lists whatever CPTs are registered on the install.
Yes. SleekView writes through wp_update_post and update_post_meta, which is what ACF and Meta Box hook into. acf/save_post, Meta Box save filters, and any save_post handler your child theme adds all fire on inline edit — bulk operations iterate through the same path.
Yes. WooCommerce orders, products, and customers each have their own SleekView integration. On Kadence sites you can combine a WooCommerce orders view with custom CPT views (lookbooks, brand pages) in a single admin surface, switching between them with tabs.
Queries hit indexed columns directly — post_type, post_status, post_date, plus any meta keys you sort on. For very large CPTs we recommend keeping aggregate columns off the default view since they're heavier; pagination is keyset where possible. Kadence's front-end performance is untouched since SleekView only loads on its own admin pages.
Yes. Configs are stored as JSON, exportable and importable across sites with the same CPT and meta-key shape. Agencies running multiple Kadence Cloud installations typically maintain a shared config repo and ship the same portfolio and case-study views to every client site.
Yes. SleekView reads database tables, not templates, so Kadence's classic theme, FSE block theme, and hybrid setups all work. The only consideration is which CPTs are registered — Kadence's own and any companion plugin's — and SleekView lists whatever's there.
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