Heroic Knowledge Base stores articles as a single custom post type, with categories and tags through dedicated KB taxonomies. The plugin writes article health to wp_postmeta: vote keys like heroic_kb_thumbs_up and heroic_kb_thumbs_down capture helpful or not-helpful clicks, and view counters keep a running total per article. Search log data flows through a separate table when search analytics is enabled.

SleekView Charts reads all of those rows directly. A card can rank articles by helpful votes, count articles per KB category, trend daily article views from postmeta timestamps, or chart the share of helpful vs not-helpful votes across the entire KB. Each card runs against the live tables, so the dashboard reflects the same article health the next reader sees.

Support managers get an at-a-glance KB health view. A Number card for total votes this week, a Pie for helpful vs not-helpful share, a Bar for top-voted articles, and an Area for daily article publishing all live on one dashboard. The data is exactly what powers the front-end vote buttons, so what the team sees and what the customer rates stays in sync.

A knowledge base is only useful if the team knows which articles are working. Heroic Knowledge Base stores helpful and not-helpful votes per article as heroic_kb_thumbs_up and heroic_kb_thumbs_down postmeta, view counts per article, and category and tag taxonomies that group articles into topics. The list screen shows all of that one row at a time but never as a dashboard.

SleekView Charts pulls those columns onto one screen. A weekly Number card for votes, a Pie for helpful share, a Bar for the top articles, and an Area for publishing rhythm all live together, refreshed against the live tables. Support sees whether deflection is climbing, writers see which topics need fresh articles, product teams see whether documentation tracks the roadmap.

The KB stops being a long list and starts being something the team manages with the same rigor as the rest of the product.