Custom Post Type UI is the most common way teams register custom post types and taxonomies without writing PHP. The plugin is good at the registration step and intentionally stays out of everything that happens after a CPT exists. Once a site has eight or ten CPTs, the standard admin lists them one by one and gives no aggregate picture of which ones are growing, which are abandoned and how their rows are distributed.

SleekView Charts reads CPTUI's registrations and queries each post type as a dataset. A Number card counts rows across every CPTUI-registered CPT. A Pie shows the row split per post type. A Bar shows top authors across the CPT family. An Area trends post creation per week so a content team can see whether "case-studies" is still being maintained or whether "events" stopped getting fresh entries six months ago.

Because each CPT is a real post type, the cards run on wp_posts and wp_postmeta directly. No separate reporting table, no nightly export. CPTUI registers, SleekView reports.

CPTUI is intentionally a registration tool. It deliberately stops at the point where the post type exists, the taxonomy is registered and the rewrite rules are in place. That is the right scope for the plugin, but it also means a site with a dozen CPTUI-registered post types has no built-in aggregate view of what is happening inside them.

The standard WordPress admin lists each CPT in the sidebar, each with its own list table. None of it adds up to a number. SleekView Charts treats the CPTs CPTUI registers as a single family of datasets.

The same wp_posts and wp_postmeta tables that store the content drive the chart cards, so the dashboard is always in sync with the editor. For a content team running on CPTUI, that converts a configuration into an observable system: which CPTs are alive, which are abandoned, which authors carry the load, which months actually shipped fresh entries. CPTUI handles the registration.

SleekView handles everything that comes after.