SleekView for GeneratePress: CPTs and meta as tables in WP Admin
GeneratePress is a renderer, not a data store — but the CPTs you register through Elements, GenerateBlocks dynamic content, or ACF still live in WordPress. SleekView reads them directly so you can sort, filter, and inline-edit without opening each post.
♾️ Lifetime License available
GeneratePress hooks let you render anything — but the admin still lists titles and dates
GeneratePress is loved for its hook system and its restraint: it stays out of your way, lets you target any element, and ships nothing you don't ask for. That makes it great for rendering CPTs in custom layouts. It does not solve the other half of the problem — managing those CPTs in the admin once you have hundreds of rows. WordPress's list table shows title, author, and date; everything else lives in wp_postmeta and stays hidden until you open each post.
SleekView reads wp_posts joined to wp_postmeta directly. The CPTs you register through GP Premium Elements, the dynamic content fields GenerateBlocks resolves at render time, the ACF or Meta Box groups attached to product or service post types — all of it becomes columns. The agent UI lists meta keys actually present on each CPT, so you compose a column set without remembering field slugs. Sub-fields in ACF groups and Meta Box repeaters are joinable.
Inline edits route through wp_update_post and update_post_meta, so the same hooks GeneratePress Elements rely on for conditional display continue to fire on save. Bulk-update fifty service-page meta values, flip a batch of testimonials from pending to approved, correct a category taxonomy across thirty case studies — every filter that would have run on a manual save still runs.
Workflow
How SleekView reads your GeneratePress 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 GP hooks and GenerateBlocks dynamic content stay accurate.
Sample columns
A typical GeneratePress service-pages view
wp_posts joined to wp_postmeta, so service, testimonial, and case-study post types registered alongside GeneratePress work without configuration changes.
wp_posts + wp_postmeta (any CPT registered by GP Premium, GenerateBlocks, or companion plugins)
| Title | Service tier | Price from | Duration | Status | Updated |
|---|---|---|---|---|---|
| Brand strategy intensive | Premium | €4,800 | 3 weeks | Published | Apr 22 |
| Logo design sprint | Standard | €1,950 | 10 days | Published | Apr 20 |
| Web copy retainer | Premium | €2,400 | Monthly | Published | Apr 18 |
| Social audit | Starter | €620 | 5 days | Draft | Apr 15 |
| Naming workshop | Standard | €1,200 | 1 week | Draft | Apr 14 |
Comparison
Default WP admin list vs SleekView on GeneratePress
Default WP admin list
- List shows title, author, date — meta keys hidden behind every post screen
- GP Premium Elements render CPT fields but don't list them
- GenerateBlocks dynamic content reads meta but doesn't surface it in admin
- No saved filtered views — every visit rebuilds filters from scratch
- Bulk meta edits require WP-CLI or a custom admin page
SleekView
-
Reads
wp_posts+wp_postmetafor any CPT alongside GeneratePress - Inline-edit ACF, Meta Box, and core meta without opening posts
- Picker lists meta keys actually present — no slug-typing
- Save filtered views per role (designer, editor, account manager)
- Switch between table, kanban, and feedback-board views
Features
What SleekView gives you for GeneratePress
Column sets matched to GP Element layouts
If a GP Premium Element renders a service page using six meta fields, build a SleekView with the same six as columns. The admin view mirrors what the front end shows, so editorial review happens at the same fidelity as rendering.
Inline edits keep your hooks intact
GP hooks, GenerateBlocks dynamic content, and any save_post handler all fire on inline edit — SleekView routes through wp_update_post and update_post_meta. Bulk operations iterate the same path; nothing is bypassed.
Filter the way you actually think
Combine status, taxonomy, and meta filters — service tier, price range, duration. Save the filter as a named view ("Premium services pending review") and reuse it across the whole team without rebuilding.
Audience
Who uses SleekView on GeneratePress sites
Agencies and freelancers on GP Premium
GP Premium Elements render polished CPT pages; SleekView gives the admin side the same level of polish. Account managers update service tiers, designers flip launch dates, and marketing reviews testimonials in one consistent table view.
Knowledge-base and docs sites
GeneratePress is a common pick for documentation themes. SleekView surfaces the doc CPT with version, last-reviewed date, and owner columns so technical writers can prioritize stale entries without opening each one.
Service-business marketing sites
Service CPTs with pricing, duration, and tier meta. SleekView shows them all together so operations can update prices across the catalog and marketing can review which services need a refreshed description.
The bigger picture
Why GeneratePress sites need an admin layer that matches the rendering layer
GeneratePress and its Premium hooks give you near-complete control over the front end. You can render any CPT in any layout, conditionally show fields, and integrate with GenerateBlocks for dynamic content that reads from meta. The admin side, by contrast, stays at WordPress core defaults — title, author, date, and a click-through to the editor for everything else.
That asymmetry shows up the moment a site grows: a docs site with two hundred entries, an agency portfolio with a hundred case studies, a service catalog with thirty pricing tiers across multiple categories. The data is rich, the rendering is sharp, but the admin treats every row as a destination instead of a row. SleekView closes the gap.
The same meta keys GP Premium Elements render and GenerateBlocks dynamic content resolves become columns in a sortable, filterable, inline-editable table. Editorial teams review at the same fidelity GP renders. Operations teams update tiers and prices in batches.
Account managers scan the catalog without clicking into every post. The data path stays exactly where GeneratePress put it — wp_posts, wp_postmeta, the hooks, the Elements — SleekView just gives the back end a workspace that matches the front end's flexibility.
Questions
Common questions about SleekView for GeneratePress
No. GeneratePress hooks and GP Premium Elements operate on rendering — front-end output, conditional display, layout assembly. SleekView operates on data — admin tables, inline edits, filtered views. They coexist cleanly: GP keeps rendering exactly as configured, SleekView gives the admin a row-level view of what GP renders.
 
Yes. GenerateBlocks dynamic content reads from postmeta and ACF fields at render time. SleekView reads the same data for the admin table view. The two are complementary: GenerateBlocks renders meta on the front end, SleekView surfaces it for editorial review and bulk updates in the admin.
Any CPT registered on the install, regardless of who registered it — GP Premium, GenerateBlocks-related plugins, ACF, Meta Box, custom code in functions.php, or third-party plugins. SleekView lists what's actually there and exposes the meta keys present on each post type.
Yes. Inline edits go through wp_update_post and update_post_meta, the same path WordPress core uses. acf/save_post, Meta Box save filters, and any save_post handlers your child theme adds run identically to a manual save in the editor.
GeneratePress is famous for fast TTFB on the front end. SleekView only loads on its own admin pages, so front-end performance is unaffected. Admin queries hit indexed columns directly; aggregate columns are opt-in per view since they're heavier — keep them off the default list and on detail views.
 Yes. Each SleekView is stored as JSON and can be exported, version-controlled, or imported into another install. Useful when you maintain multiple GeneratePress sites with similar CPT structures and want consistent admin views without rebuilding column sets each time.
 
Yes. SleekView reads database tables, not templates. Whether you're on a classic GeneratePress setup, an FSE-compatible block theme, or a hybrid, the data path is the same — wp_posts and wp_postmeta — so SleekView works without theme-specific configuration.
SleekView joins wp_term_relationships and wp_terms when you add a taxonomy column or filter. Service categories, doc-version tags, and custom taxonomies appear as filterable columns. Bulk-update of taxonomy terms goes through wp_set_object_terms so any taxonomy hook your code or GP Elements depend on still fires.
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