For pattern usage charts, yes. SleekView scans post_content for pattern references to compute usage counts and caches the result per view. Other cards (type share, edit cadence) read standard columns without parsing markup, so dashboards stay fast even on large sites.

By scanning post_content across the post catalogue for the matching pattern reference and aggregating counts per pattern. The scan is cached per view so charts stay responsive; refresh when an audit needs current numbers after a content push.

Yes. The sync state is a column on each wp_block row. A Pie grouped by sync_state shows the split between synced and unsynced patterns, useful for design-system governance and for spotting drift after a bulk import.

Yes. Cwicly stores dynamic-data references inside block markup with selected attributes mirrored to postmeta. SleekView decodes the high-level parts and can group patterns by referenced data source for migration-prep charts.

No. Chart filters are dashboard-level read filters; they don't write to the database. Inline writes from the table view route through wp_update_post and update_post_meta, which is where Cwicly's caching invalidates.

Yes. The post_type column distinguishes wp_block, wp_template, and wp_template_part. Filter the dashboard to wp_template_part for a parts-only view, or use the type-share Pie to see all three in context.

Yes. Standard queries against wp_block use post-type indexes; pattern-usage scans are cached per view to avoid re-scanning post_content on every render. Sites running hundreds of patterns and thousands of pages render the dashboard smoothly.

Yes. Each card exports its underlying filtered rows to CSV, and the full dashboard exports as a PDF. The design-system review becomes narrative on top of pre-aggregated charts, not a spreadsheet rebuild per audit cycle.