SleekView Charts for PublishPress Blocks
PublishPress Blocks adds extra blocks, role-based permissions and schedule rules on top of the block editor. SleekView Charts reads block usage from post_content, permission settings from options and schedule metadata, and renders it all as Number, Pie, Bar and Area cards.
♾️ Lifetime License available
A block library is only useful if you can see how it is being used
PublishPress Blocks (formerly Advanced Gutenberg) extends the block editor with a roster of additional blocks, role-based permission rules, scheduled block visibility and per-block style controls. It is one of the most common ways to make a multi-author site usable across designers, editors and contributors. The trouble is that block usage data lives where it has always lived: parsed out of post_content, scattered across thousands of posts.
SleekView Charts walks post_content for each post and counts blocks by name, joins that with the post type and last update, and reads the plugin's permission settings from wp_options to expose which roles have which blocks enabled. A Number card shows the total uses of the Advanced Table block. A Pie splits usage across all PublishPress Blocks types. A Bar counts blocks enabled per role. An Area trends block insertions by month so a design system rollout becomes visible.
The plugin keeps owning the editor experience. Permissions, scheduled visibility and per-block settings remain in the existing PublishPress Blocks admin. SleekView just turns the resulting block usage and configuration into a real reporting layer, so design system owners and editorial leads can see what is actually being used.
Workflow
Turn block library usage into a dashboard
Parse blocks from post_content
Read permission settings
Compose chart cards
Save and share
Sample dashboard
Charts you can build from PublishPress Blocks data
Advanced Table uses
Count
Block usage mix
Count
group by block_name
Blocks enabled per role
Count
group by role
Block insertions over time
Count
group by post_modified
Comparison
Default PublishPress Blocks admin vs SleekView Charts
Default PublishPress Blocks admin
- No aggregate view of how often each block is actually used
- Permission settings show as toggles, not as a chart of coverage per role
- Block adoption over time is not surfaced anywhere
- Reusable block reuse counts are not exposed in the admin
- Cross-post block usage queries need a custom WP_Query loop
SleekView Charts
- KPI card for total uses of any specific block
- Pie of the full block usage mix across the site
- Bar of blocks enabled per role for permission audits
- Area trend of block insertions to measure adoption
- Filters carry from the chart view into the underlying SleekView table
Features
What SleekView Charts gives you for PublishPress Blocks
Block library as data
Every block in every post becomes a row. Counts, splits and trends across the whole library appear as chart cards without writing a single parse_blocks loop.
Permission map as a chart
The PublishPress Blocks role permission map is read from wp_options and rendered as a Bar of enabled blocks per role. Permission drift after onboarding or offboarding stops hiding in toggles.
Adoption curves
Trend block insertions by month or week so a new block in the library has a real adoption curve. Design system rollouts get a number instead of an anecdote.
Audience
Who builds PublishPress Blocks charts dashboards with SleekView
Design system owners
See which blocks are being used, which never got picked and where to invest variant work. The block library becomes a measurable surface, not a hope.
Site admins
Audit which roles have which blocks enabled after a permission change. Catch a contributor with the Advanced Code block accidentally enabled before it ships to production.
Editorial leads
Pin a block usage pie to the editorial dashboard and use it to brief writers on which layouts the team should reach for first in the upcoming sprint.
The bigger picture
Why a block library needs a reporting layer
Block libraries are easy to add and hard to keep relevant. PublishPress Blocks gives a team a roster of extra blocks, role-based permissions and scheduled visibility, all of which are valuable on a multi-author site. The risk is the same risk every component library faces: half the blocks dominate every page, a quarter rarely get used and the rest never get picked, while permission rules drift quietly after every team change.
The default admin shows configuration but not consumption. SleekView Charts pulls block usage data straight from post_content and permission settings straight from wp_options, and turns both into Number, Pie, Bar and Area cards. Design system owners get an honest picture of what the team is reaching for, admins get a permission audit they can scan in five seconds, and editorial leads get a single dashboard to point at when planning the next round of templates.
Questions
Common questions about SleekView Charts for PublishPress Blocks
From parse_blocks() on each post's post_content. SleekView walks the parsed block tree and counts occurrences of each block name, including nested inner blocks. The same data WordPress already uses to render the post is what drives the chart cards.
 Yes. The free plugin already registers its blocks and writes its permission map to wp_options, which is exactly the data SleekView reads. Pro features add extra blocks and additional settings, which become extra chart dimensions but are not required for the base reporting.
 Yes. PublishPress Blocks writes schedule metadata onto blocks that have visibility rules. SleekView reads those attributes from the parsed block tree, so a Pie of currently visible versus hidden scheduled blocks is one of the available cards.
 Yes. Reusable blocks live in the wp_block post type and are referenced by ID from post_content. SleekView resolves those references so a Bar of reusable block reuse counts shows which patterns the team actually leans on.
 Yes. Add a filter for post_type and the whole dashboard narrows to that scope. Useful for sites that ship landing pages, blog posts and product pages with different block usage expectations and want each one as its own dashboard.
 No, in practice. SleekView caches parsed block counts per post and refreshes only on post update. The first build of a heavy site walks the corpus once and incremental updates run in milliseconds after that.
 Yes. Block occurrences carry the post_author through to the chart layer. A Bar grouped by author with a filter on block_name surfaces which writers reach for which blocks the most, which is useful for design system training and template handoffs.
 Yes. Any filtered set behind a chart card exports as CSV with the underlying block occurrences and post columns. Design system owners typically use this for quarterly audits, and admins use it to document role permission settings before a major user clean-up.
 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