SleekView Kanban for WPGraphQL for ACF
SleekView Kanban reads WPGraphQL for ACF field group exposure settings stored on every ACF field group, groups them by exposure state, and lets API leads drag ACF field groups between Draft, Internal, Public, and Deprecated columns for the schema review.
♾️ Lifetime License available
Why WPGraphQL for ACF sites need a kanban view
WPGraphQL for ACF adds a "Show in GraphQL" toggle and a GraphQL field name to every ACF field group, which exposes ACF fields through the WPGraphQL schema. Those settings live in the standard ACF field group post (the acf-field-group post type) as part of the field group settings array stored in post content, alongside the rest of the ACF field group definition for the site running the headless backend.
SleekView Kanban points at the acf-field-group post type, lets you pick an exposure state meta key or a derived state from the Show in GraphQL toggle as the group field, and renders one card per ACF field group. Each card shows the field group title, the GraphQL field name, the WordPress location rule (post type, taxonomy, options page), the assigned API lead, and the timestamp of the last change for context.
When an API lead drags a card from Draft into Internal or Public, SleekView calls update_post_meta for the exposure state key on the acf-field-group post, fires standard ACF save hooks, and updates column counts. Custom code listening to standard hooks continues to fire.
Workflow
Build a WPGraphQL ACF board in four steps
Connect SleekView ACF
Pick an exposure state key
Set what shows on cards
Enable drag-and-drop rules
Sample board
Sample WPGraphQL for ACF review board
Comparison
Default WPGraphQL ACF vs SleekView Kanban
Default ACF admin view
- ACF shows every field group as a row in a flat list with standard columns.
- WPGraphQL for ACF toggles live in field group settings with no visual queue.
- Bulk actions cannot group field groups by exposure state across the dashboard.
- Filtering by exposure state is not supported, leads cannot drag between rows.
- API leads write custom admin pages to give field groups a board-like surface.
SleekView Kanban
-
Group
acf-field-groupposts by exposure state meta or Show in GraphQL. - Show GraphQL field name, location rule, lead, and timestamp on the card front.
-
Drag a card from Draft into Internal and SleekView calls
update_post_meta. - Run one board for ACF field groups and another for WPGraphQL persisted queries.
- Roles can be limited to API leads so general subscribers never see the board view.
Features
What SleekView Kanban gives you for WPGraphQL for ACF
Review for every field group
Every ACF field group exposed through WPGraphQL for ACF lands on the board with an exposure state meta key defining columns. API leads skip custom admin pages, and the standard ACF save lifecycle stays intact through every move.
Name, location, lead on cards
GraphQL field name, location rule, lead, and timestamp land on the card front, so a reviewer sees what the field group exposes and where it applies without opening the field group. ACF save hooks fire on every move.
Drag writes via update_post_meta
When a card moves, SleekView calls update_post_meta for the exposure state key on the acf-field-group post, the same function the editor uses on save. The standard ACF save hooks fire on every change.
Audience
API leads that put it on the field group dashboard
Headless field group review
Headless teams promote ACF field groups through Draft, Internal, and Public for the frontend app. The board shows which groups the frontend reads, and ACF save hooks keep caches in sync.
Security auditing exposed fields
Security teams audit which ACF field groups the WPGraphQL schema exposes. Deprecated tracks sunsets, Internal surfaces groups that should never be public, and the board keeps the schema honest.
Platform field group rollout
Platform teams roll out shared ACF field groups across many WPGraphQL sites. Draft tracks new groups in design, Public marks the shipped surface, and the board doubles as a recent-history view.
The bigger picture
Why a WPGraphQL ACF kanban governs the schema
WPGraphQL for ACF is how a headless WordPress site turns ACF field groups from an editor-only convenience into a real part of the public GraphQL schema. Every field group with Show in GraphQL turned on is a public contract with whatever consumes the schema, and the cost of an accidental exposure or a silent breaking change ripples through every frontend that reads the field group. The default ACF admin shows every field group as a row in a flat list with the standard title and location columns, which works for a few field groups but turns into a wall of rows once a site has thirty or more field groups across several teams.
A kanban view changes that shape. An exposure state meta key becomes the columns, the most important settings land on the cards, and the board gives the schema review team a real surface without writing a custom admin page. Public shows the shipped surface, Internal tracks editor-only field groups, and Deprecated documents sunsets in plain sight.
Questions
Common questions about SleekView Kanban for WPGraphQL for ACF
Yes. Moving a card calls update_post_meta for the exposure state key on the acf-field-group post, the same function the editor uses on save. The standard ACF save hooks and any custom code listening to the standard WordPress hooks continue to fire without any extra plugin glue.
SleekView reads the acf-field-group post type through standard WP_Query and post meta, which is where ACF stores field group definitions. You pick the source, choose an exposure state meta key to group by, and SleekView renders one card per field group with the settings you select.
Yes. SleekView ships with role-based permissions, so API leads can have a single page that holds the field group review board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move groups into Public without approval.
Derived states are first-class in SleekView. You can define a workflow_state computed from several settings, such as treating a field group as Deprecated when a sunset flag is true and Show in GraphQL is still on, and SleekView groups field groups by that derived value across columns.
Each board has one source so the rules stay clear, but most setups run one board for ACF field groups and a second board for WPGraphQL persisted queries on the same governance dashboard. Column counts at the top of each show waiting work at a glance for the team.
Dragging never deletes data. It calls update_post_meta for the exposure state key on the acf-field-group post, which is the same thing a save in the editor does. Other ACF settings, the Show in GraphQL toggle, and the GraphQL field name are not touched, so settings remain as saved.
Yes. Each card can show the time since the field group was last modified or since the exposure state key was last updated, so a field group stuck in Draft for a quarter looks visibly different from a fresh one. Sort options can place the oldest cards at the top of every column.
No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the wp_posts table and the post meta key. Sites with hundreds of ACF field groups stay responsive because heavy field definitions are only fetched for cards currently on screen.
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