Directly from wp_posts. SleekView scans the post_content column for getwid/* block comments that Gutenberg writes when an editor inserts a Getwid block. The block names are parsed into a column SleekView can group on. Chart cards reflect current data as soon as a post is saved through the standard WordPress update path.

Yes. Group a Donut or Bar card by the parsed Getwid block name and SleekView splits the chart across getwid/section, getwid/advanced-heading, getwid/image-stack-gallery, getwid/post-carousel, getwid/price-list, getwid/instagram, getwid/social-links, and the rest of the forty-plus blocks in the namespace.

Group an Area or Line card by post_modified truncated to week or month, aggregated by Count, filtered to rows whose post_content contains a getwid/* block. The curve shows when Getwid content is being touched, useful for tracking campaign cadence, freeze windows, and stretches of zero activity that mark stale pages ready for review.

Yes. View-level filters such as post type, status, author, and date range apply to every chart card on the dashboard. One saved configuration drives both the audit table view and the chart view, so block-usage housekeeping and reporting stay in sync without keeping two separate views aligned by hand.

Yes. The base query hits indexed columns on wp_posts (post_type, post_status, post_modified, post_author). The getwid/* block name extraction is cached per post so the group-by column reads from a small lookup, keeping the dashboard fast even on large sites with thousands of posts running Getwid layouts.

Yes. Group a Bar card by post_author and aggregate by Count over rows whose post_content contains a getwid/* block. The chart resolves IDs against wp_users and renders display names, so ownership of Getwid-built content is clear when planning training, handover, or migration off a specific Getwid block type.

Charts are read-only summaries by design. To act on a chart insight, switch to the audit table filtered to the same slice (for example the stale segment of a block-type donut) and open the post directly in the Gutenberg editor. Edits route through the standard WordPress update path so every Getwid block renders exactly as before.

Getwid does not ship a reporting screen for its own block usage, so there is nothing to replace. SleekView Charts adds a reporting surface on top of the post_content WordPress and Getwid already write, so the plugin keeps owning the editor experience and the chart view owns the summary across the whole site.