SleekView for WPGraphQL Pro: schema-backed data as admin tables
WPGraphQL Pro exposes WordPress content (posts, terms, users, custom fields) as a typed GraphQL schema on top of wp_posts, wp_postmeta, and wp_users. SleekView reads the same underlying data so editors get a workable admin without writing a GraphQL client.
♾️ Lifetime License available
An admin table for the data your GraphQL clients already use
WPGraphQL Pro builds on the WPGraphQL ecosystem to expose WordPress data as a strongly typed GraphQL schema. Posts come from wp_posts, fields from wp_postmeta (with WPGraphQL for ACF or Meta Box bridging custom fields), terms from wp_terms, and users from wp_users. The Pro layer adds caching, smart cache invalidation, ACF Pro field support, and access control on the GraphQL endpoint, which makes headless and decoupled WordPress sites much more practical.
What WPGraphQL Pro doesn't change is the WordPress admin underneath it. Editors still get the default edit.php list table, which doesn't expose meta fields or related content as columns, doesn't sort on meta, and doesn't filter on arbitrary fields. SleekView reads the same data WPGraphQL Pro exposes, just from the database side, so the admin finally matches what the GraphQL schema already describes.
Inline edits route through WordPress core update APIs and through ACF or Meta Box where applicable, so the next GraphQL query returns the new state immediately. WPGraphQL Pro's smart cache invalidation fires on the same save_post and meta-update hooks SleekView uses, which means cached GraphQL responses invalidate normally on every cell save.
Workflow
From WPGraphQL Pro schema to a workable admin
Pick a content type
Compose columns
wp_postmeta and wp_term_relationships only for the columns you pick.
Filter and group
Edit through core APIs
wp_update_post, update_post_meta, wp_set_object_terms, ACF, or Meta Box. WPGraphQL Pro's cache invalidates on the same hooks.
Sample columns
A typical WPGraphQL Pro-backed CPT in admin
wp_posts + wp_postmeta + wp_users + wp_terms (the same tables WPGraphQL Pro's resolvers read)
| Title | Author | Category | Featured | Updated | Status |
|---|---|---|---|---|---|
| Headless rollout | Alex Reyes | Engineering | Yes | Apr 22 | Published |
| Schema cleanup | Ria Bell | Engineering | No | Apr 23 | Draft |
| Cache audit | Tom Park | Performance | Yes | Apr 24 | Published |
| Deprecated guide | Mia Lin | Docs | No | Jan 12 | Trashed |
Comparison
Default WP admin vs SleekView for WPGraphQL Pro
Default WP admin
- Default list tables show none of the meta fields WPGraphQL Pro exposes as schema types
-
Sorting on
wp_postmetaneeds custompre_get_postshandlers per CPT -
Filtering on ACF or Meta Box fields isn't first class in
edit.php - Related content across types isn't visible inline
- Sharing a curated admin column set per role means a custom list table
SleekView
- Admin columns that mirror the GraphQL schema
- ACF and Meta Box fields as sortable columns via the same registry
-
Filters across
wp_postmeta, taxonomies, and authors - Inline edits trigger WPGraphQL Pro cache invalidation normally
- Saved views per role for editorial, dev, and ops teams
Features
What SleekView gives you for WPGraphQL Pro
Schema-aligned columns
Every field WPGraphQL Pro exposes through ACF, Meta Box, or core post fields is available as a SleekView column. The admin starts to look like the schema your front end already consumes.
Smart cache stays sharp
WPGraphQL Pro's smart cache invalidation hooks save_post and meta-update hooks. SleekView writes through the same core APIs, so cached GraphQL responses invalidate correctly on every cell edit.
Inline edit through core
Cells write through wp_update_post, update_post_meta, ACF's update_field, or Meta Box's rwmb_set_meta, so the next GraphQL query returns the new state immediately.
Audience
Who uses SleekView for WPGraphQL Pro
Headless WordPress teams
Editors need an admin that matches the GraphQL schema the front end consumes. SleekView turns the same underlying data into a table that mirrors what queries already return.
Platform engineering
Stop maintaining bespoke manage_*_columns filters for every headless site. SleekView gives a generic admin table that updates as the schema evolves.
Editorial teams
Sort drafts by deadline, filter by category, and update statuses inline. The columns are the ones the front end already uses, so editors stop guessing what the public site shows.
The bigger picture
Why headless WordPress needs the same admin
WPGraphQL Pro made headless WordPress practical for serious teams. The schema is typed, the cache is smart, and ACF and Meta Box bridges keep the field plugin you already have. The admin underneath it, though, hasn't moved.
Editors still open edit.php and see title, author, and date by default, even when the GraphQL schema the front end uses already describes a dozen meta fields and several relationships. The gap between what the front end consumes and what the admin shows is the source of most editor confusion on headless sites. SleekView closes that gap by reading the same underlying tables and turning them into an admin table that mirrors the schema.
Writes route through WordPress core and through ACF or Meta Box, so WPGraphQL Pro's invalidation continues to fire and cached responses stay sharp. Front-end clients keep using GraphQL. Editors get an admin that finally matches the data the front end already sees.
Questions
Common questions about SleekView for WPGraphQL Pro
No. SleekView reads from the database directly, not through the GraphQL endpoint. That keeps admin reads fast and avoids competing with WPGraphQL Pro's cache. The data is the same because both read wp_posts, wp_postmeta, wp_terms, and wp_users.
Yes. WPGraphQL Pro's smart cache invalidation listens for save_post, updated_post_meta, and related core hooks. SleekView writes through those same APIs, so cache invalidation behaves exactly as it would on an edit through the post editor.
Yes. SleekView reads ACF fields through ACF's registry and writes through update_field, which means WPGraphQL for ACF sees consistent values on the next query. Field group structures are respected.
Yes. Meta Box fields are read through Meta Box's registry and written through rwmb_set_meta. Both default postmeta storage and Meta Box's custom-table storage option work.
WPGraphQL Pro controls the public schema. SleekView is admin-only, so access to a view is governed by WordPress capabilities and SleekView's per-role permissions. Both layers can coexist: GraphQL access controls the public endpoint, SleekView controls the admin.
Yes. Anything bound to save_post, updated_post_meta, or ACF's update hooks fires on cell edits. That's how WPGraphQL Pro's invalidation knows to clear cached responses, and why SleekView stays consistent with whatever else listens to those hooks.
Yes. Any SleekView exports to CSV from the table header with active filters and column order respected. The export reads from the same query the table is showing, useful for content audits and backups.
Yes. SleekView paginates against the same indexes WordPress uses, and the meta joins are scoped to chosen columns. Headless sites that already have GraphQL caching benefit because admin reads don't go through the endpoint and don't compete with it.
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 checkoutBrowse more
- Woocommerce Google Product Feed
- Woocommerce Correios Brazil
- Woocommerce Referrals
- Woocommerce Product Question
- Yith Woocommerce Wishlist
- Woocommerce Bulk Discounts
- Yith Woocommerce Zoom Magnifier
- Mvx Marketplace
- Woocommerce Conditional Shipping
- Linnworks Wp
- Woocommerce Variation Stock
- Woocommerce Nowpayments
- Woocommerce Side Cart
- Woocommerce Pinterest Feed
- Woocommerce Conditional Shipping And Payments