The Content Views alternative for views beyond grid and list
Content Views is a popular plugin for rendering posts and CPTs as grids, lists, and sliders. SleekView covers grid and list layouts and adds tables, kanban boards, and feedback boards over CPT, ACF, and Meta Box data, with field-driven filters and inline editing.
♾️ Lifetime License available
When the listing outgrows grid and list
Content Views (from PT Guy Labs) is one of the more widely installed grid plugins on the WordPress repo, with a free version that handles grids, lists, and basic filtering, plus a Pro tier that adds sliders, custom fields, and additional layouts. For a homepage feed, a category landing, or a portfolio block, it is a familiar and capable pick.
SleekView reads the same kind of data (CPTs, ACF, Meta Box) and renders it as a grid (the case Content Views covers), or as a table, kanban board, or feedback board. Filters, search, sort, and pagination are part of every view, and editors can update fields inline. Slider and carousel layouts are not part of SleekView's scope; for sites whose primary need is a slider, Content Views remains a fair fit on that one layout.
The migration story is strongest for teams whose listings are slowly turning into working tools. The blog grid is fine, but the next listing is a sortable directory of services, the one after that is a board of releases by status, and the one after that is a feedback page with upvotes. Content Views does not cover those, and SleekView covers them in one configuration model alongside the original grid.
Workflow
How a Content Views embed becomes a SleekView
Pick the data source
Choose the layout
Configure filters and sort
Embed and verify
Comparison
SleekView vs Content Views at a glance
Differences
What changes when you move off Content Views
The Content Views way
- Layouts limited to grid, list, slider, no table or kanban
- Output is read-only display, no inline editing
- Custom field display is gated to the Pro tier
- Filtering is mostly taxonomy-driven, not field-driven
- Best fit is the content-showcase case, not internal tools
The SleekView way
- Grid, list, table, kanban, and feedback views in one plugin
- ACF and Meta Box support across every view, not tier-gated
- Inline editing and kanban drag-to-update on CPT data
- Field-driven filter, sort, and search toolbar
- Embeds via shortcode or block in any builder
Features
Three things that actually change how you work
More than grid and list
Content Views covers grids and lists well. SleekView adds the layouts that grid plugins typically do not ship: sortable tables, status-grouped kanban boards, and upvote-driven feedback boards. The same CPT and fields drive all of them.
Custom fields without a Pro upsell
In Content Views, displaying ACF or Meta Box fields generally requires the Pro tier. SleekView ships ACF and Meta Box support as core, with no separate add-on or tier required to show, filter, or sort by custom fields.
Editing inside the view
Content Views renders posts; updating them happens in the WP admin. SleekView lets editors update fields inline. Click a table cell, drag a kanban card to a new column, toggle a select directly in the row. Edits go through standard CPT and field hooks.
Migration
Moving from Content Views to SleekView
1. Inventory each Content Views instance
List every Content Views block or shortcode on the site, the post type or taxonomy it reads, the layout chosen, and which features come from the Pro tier.
2. Build matching SleekViews
Recreate each view as a SleekView pointed at the same data source. Use grid for the blog-style cases or move to table or kanban where the listing has grown into something more structured.
3. Move ACF and Meta Box fields onto views
Any custom field that needed Content Views Pro to display can be added directly to a SleekView column, card slot, or filter input. No separate add-on required.
4. Swap embeds and retire the Pro license
Replace Content Views embeds with SleekView equivalents on each page. Verify rendering. Once the static grid use cases are covered, the Pro license can be allowed to lapse if no slider instances remain.
Audience
Where teams move from Content Views to SleekView
Sites moving from feeds to working tools
Projects that started with a few content grids often grow into editorial dashboards, internal directories, or roadmap boards. SleekView covers the original grid and the operations table over the same CPT.
Custom-field-driven listings
Where the listing depends on ACF or Meta Box fields, Content Views requires the Pro tier and Content Views Pro's custom-field controls. SleekView treats custom fields as core across every view type.
Editors who update records often
Once a view is part of an editor's daily workflow, leaving the page to edit a record adds friction. Inline cell editing and kanban drag-to-update keep editing in the view itself.
The bigger picture
Why custom fields and multiple view types belong in core, not Pro
Content Views is one of the more honest grid plugins in its category: the free version does grids and lists, the Pro version handles custom fields and additional layouts, and the upgrade path is clear. The interesting question is whether splitting custom-field support across tiers still makes sense for the kind of WordPress site that needs structured listings in the first place. Almost every project that wants a grid past a basic blog feed turns out to need ACF or Meta Box fields on the cards, which puts custom-field display on the upgrade-or-do-not-build side of the line.
SleekView takes a different angle. The same plugin reads CPT, ACF, and Meta Box from day one, across grid, list, table, kanban, and feedback views, with no separate tier or add-on. The longer-term value is consolidation.
One filter toolbar shape, one set of card slots, one set of hooks, across every type of view the project actually wants to ship. There is also a maintenance angle that gets glossed over in feature comparisons. A site running Content Views plus a separate kanban plugin plus a separate feedback plugin has three release cycles to track, three settings UIs to learn, and three styling models to reconcile.
Consolidating to SleekView reduces that footprint to one. The slider case stays a fair argument for Content Views, since that layout is genuinely out of SleekView's scope. Outside of that one layout, replacing Content Views with SleekView is mostly about not paying for custom-field support tier-by-tier and not assembling separate plugins for tables, kanban, and feedback.
The grid layout still renders; it just stops being the only shape of view the project can build.
Questions
Common questions about switching from Content Views
For the grid, list, and custom-field cases that the Pro tier unlocks, yes. SleekView ships ACF and Meta Box support as core, plus tables, kanban, and feedback boards that Content Views does not include at any tier. For slider and carousel layouts, Content Views Pro remains a better-shaped tool because SleekView does not target carousel rendering.
Usually not. Both plugins read the same kind of source data (posts, CPTs, taxonomies, ACF, Meta Box) and embed via shortcode or block. The migration is largely configuration work: recreate each view, swap the embed, verify side by side, retire the original. There is no schema change because the records stay where they are.
Yes. Taxonomies are first-class filter and grouping options in SleekView, alongside ACF and Meta Box fields. The filter toolbar treats them the same way Content Views does, with multi-select, search, and dependent filters supported.
SleekView's grid and table views adapt to screen width via responsive breakpoints in CSS. Grid columns collapse, tables become scrollable or stack, and kanban columns become horizontally scrollable on narrow screens. The behaviour is similar to Content Views's responsive grids.
Yes. They do not share storage, hooks, or rendering. A site can keep Content Views for slider instances and use SleekView for grids that are migrating toward tables or kanban. Most teams eventually consolidate on whichever covers more of their current use cases.
Content Views has a free tier with a Pro license for custom fields, sliders, and additional layouts. SleekView is sold standalone or as part of the Sleek All Access Pass. For sites that only need a grid block, the Content Views free tier is cheaper. For sites that need custom fields or multiple view types, SleekView usually replaces multiple plugins.
No. SleekView renders via a shortcode and a Gutenberg block, so it works in plain Gutenberg as well as Elementor, Bricks, Oxygen, Cwicly, and Breakdance. The same view config renders identically in any of those contexts.
SleekView ships card and toolbar styles that respect typical theme typography and spacing. Sites that heavily customised Content Views Pro templates will have some restyling work, but the underlying data and fields stay the same, so the migration is configuration work, not data work.
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