CM Knowledge Base (by CreativeMinds) stores articles as a custom post type with categories and tags as taxonomies. Rating votes, view counters, and (with the analytics add-on) failed-search logs live across cmkb_-prefixed CreativeMinds tables and wp_postmeta. The default WordPress list does not surface that telemetry, which is the only data that tells editors what to fix next.

SleekView reads the article CPT, joins the CreativeMinds analytics tables, and lifts postmeta rating counters into columns. Editors get a flat table where each article shows category, helpful and not-helpful votes, views, and last-updated date. Filters compose across those columns, so a saved view of articles with low ratings and high views, or with high search-log counts but low article matches, becomes one click. The signal that decides editorial priority becomes visible at list level.

Inline edits cover status, category reassignment, and the featured flag. Writes go through wp_update_post and update_post_meta so any sitemap, search index, or front-end cache that hooks save_post refreshes as it would from the post-edit screen. CSV export of any saved view supports monthly editorial reporting without dumping raw cmkb_ tables.

Knowledge bases drift without anyone noticing. The articles published in launch month answer questions that no longer apply, while customer queries shift to features documented two years ago in a buried article. CM Knowledge Base captures the right telemetry, ratings, views, search misses, but spreads it across CreativeMinds tables and postmeta where editorial leads can't act on it.

A single screen showing rating, views, age, and search-gap counts across the whole KB lets a content lead spend forty minutes a week on what would otherwise need a custom report or a SQL dump. The articles that need rewrites surface themselves, the search terms that need new articles surface themselves, and the editorial work prioritises itself. SleekView delivers that without forking how CM Knowledge Base stores data.

The same CPT, the same cmkb_ tables, the same hooks, but now in a table that surfaces what an editorial lead actually needs to decide what to fix next.