Docs Pro keeps articles as a custom post type with categories and tags as taxonomies, plus feedback counters, view totals, and ordering values written to wp_postmeta. The default list shows title, category, and date, which is useful for browsing but not for editorial work. Helpful and not-helpful counts, view totals, and category coverage all sit in postmeta where they can't be sorted or filtered without opening every article.

SleekView reads the article CPT and surfaces those postmeta keys as first-class columns. A typical run starts with a view of articles updated more than six months ago, sorted by views descending, to find high-traffic but stale content. A second view filters where not-helpful exceeds helpful, sorted by views, to expose the worst-performing articles that are still getting traffic. Both views save and reload as a single click.

Inline edits cover status, category, featured flag, and ordering values. All writes go through wp_update_post and update_post_meta so any sitemap, search index, or cache layer that hooks save_post refreshes the same way it would from the post-edit screen. CSV export of any saved view gives editorial leads a shareable snapshot without manual data wrangling.

Knowledge bases drift without anyone noticing. The articles published in launch month answer questions that no longer exist, while customer queries shift to features documented two years ago in a buried article. Support teams feel it first, a question keeps recurring because the article that answers it is wrong, outdated, or never got rewritten when the UI changed.

Without a proper editorial view, the only signal of decay is a complaint or a deflection-rate drop, both lagging indicators. Helpful and not-helpful counts are the leading indicator. Docs Pro captures them faithfully but stores them in postmeta where editorial leads can't act on them without opening each article.

A single screen showing rating, views, and age across the whole knowledge base lets a content lead spend forty minutes a week on what would otherwise need a custom report or a data export. The articles that need attention surface themselves, the articles doing fine stay quiet, and the editorial work prioritises itself.