BetterDocs models a knowledge base as a custom post type (docs) with categories and tags as taxonomies, plus analytics counters (views, helpful votes, unhelpful votes) stored in _betterdocs_* postmeta. The default plugin admin shows articles as a stock WordPress post list. Editorial decisions like "which articles in the Billing category have low helpful-vote ratios and haven't been updated in 90 days?" require either an export or manual filtering.

SleekView reads wp_posts with post_type=docs and the matching wp_postmeta rows, then pivots them into a sortable, filterable table. Category, tag, last-updated date, view count, helpful-ratio, and assigned author become first-class columns. Saved views like "Billing articles with helpful ratio below 60%, sorted by view count descending" become one-click reloads for the docs team's weekly review.

Inline edits to status, category, and assigned author route through WordPress core functions (which is how BetterDocs reads them on its side) so BetterDocs caches invalidate normally and the front-end help center reflects changes immediately.

Knowledge bases age in a way blog posts do not. A blog post is a snapshot in time; an article is a contract with users that the documented behaviour matches the product. When the product changes and the article doesn't, the article actively does harm: users follow stale instructions, fail, and open support tickets that should never have existed.

BetterDocs gets the publishing surface right and stores enough analytics signal to detect which articles are drifting (helpful-vote ratios, view counts, last-updated dates). What it doesn't ship is an editorial triage view that lets a docs team find the rotting articles before users do. SleekView fills that gap without adding any new data model.

Helpful ratios derive from existing postmeta, last-updated dates come from post_modified, categories drive saved-view scopes, and inline status and category edits route through WordPress core so BetterDocs caches invalidate normally. The weekly editorial review becomes a single screen: open the saved view, sort by helpful-ratio ascending filtered by last-update over 90 days, work through the top 10 articles, ship updates. The knowledge base stays accurate, which is the whole point of having one in the first place.