WPGraphQL for ACF gives every Advanced Custom Fields group a show_in_graphql checkbox. Tick it and the fields surface on the matching GraphQL type. The plugin does its job perfectly per group. The site-level picture, which groups are exposed, which types they hang off, which fields actually get queried by the frontend, only lives across hundreds of ACF posts and the WPGraphQL query log.

SleekView Charts reads the acf-field-group post type (where show_in_graphql lives in the group settings JSON) and joins it to WPGraphQL's logged operations. A Number card counts exposed groups. A Pie splits exposed fields by ACF field type so the schema owner sees how much of the surface is plain text against repeaters or relationship fields. A Bar groups query volume by exposed field name to spot fields that nobody on the frontend actually reads. An Area trends new exposures over time, which is the fastest way to catch "we accidentally exposed the internal admin notes group" before it ships.

Everything reads from data ACF and WPGraphQL already write. The dashboard works on every install that has both plugins active, with no extra schema generator and no parallel registry to keep in sync.

WPGraphQL for ACF makes exposure trivial: one checkbox per group, applied to dozens of groups across content types over months. Each individual decision feels safe in isolation. The cumulative public schema is the part that nobody owns.

A site that started with a few exposed groups ends up exposing relationship fields that point at user meta, repeaters that load thousands of subfield rows per query and admin-only notes that should never have left the WP backend. A KPI of exposed groups makes the surface countable. A pie of field types makes the shape honest.

A bar of query volume separates the fields the frontend really needs from the long tail. An area trend of new exposures lets a schema review catch leaks before they ship. Same checkbox flow, completely different governance posture.