✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Minerva KB: knowledge base articles as tables

Minerva KB stores articles as the minerva-kb custom post type with categories, tags, and feedback votes stored as wp_postmeta keys. SleekView pivots that into a flat editable table so editors can audit, triage, and edit inline.

♾️ Lifetime License available

SleekView table view for Minerva KB

Minerva KB editorial review on one screen

Minerva KB keeps articles as the minerva-kb custom post type with categories and tags as taxonomies. Feedback votes (helpful, not-helpful), view counters, and any custom ordering values are stored as wp_postmeta. The default WordPress list shows title, author, and date, useful for browsing but not for editorial work. Vote counts, view totals, and category coverage all sit in postmeta where they cannot be sorted or filtered without opening each article.

SleekView reads the minerva-kb CPT and surfaces those postmeta keys as first-class columns. A typical editorial 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 still getting traffic. Both views save and reload as a single click.

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 cache layer that hooks save_post refreshes as it would from the post-edit screen. CSV export of any saved view gives editorial leads a shareable snapshot in seconds.

Workflow

From minerva-kb posts to an editorial dashboard

1

Map postmeta

SleekView reads the helpful, not-helpful, and views counters Minerva writes to postmeta on each minerva-kb article and exposes them as numeric columns ready for sort and filter.
2

Build review filters

Save views like 'last-updated > 6 months AND views > 1000' or 'not-helpful > helpful' to surface stale or low-rating content. The query saves once and reloads in one click.
3

Audit categories

Combine taxonomy filters across category and tag in a single view to spot coverage gaps, overlapping topics, or single-article categories that should merge with a sibling.
4

Edit inline

Reassign categories, toggle status, or change the featured flag from the row. Standard save_post hooks fire so the front-end search index and any caching layer rebuild as expected.

Sample columns

A typical Minerva KB articles view

One row per article with category, helpful votes, views, and last update.
Source: wp_posts (post_type=minerva-kb) + wp_postmeta + wp_term_relationships
Title Category Helpful Not helpful Views Updated
Two-factor authentication setup Security 178 10 13.6k Apr 16
Webhook signature verification API 79 6 4.9k Apr 04
Legacy CSV column map Imports 16 23 1.5k Aug 30
Discontinued v0 SDK API 2 27 338 Feb 11

Comparison

Default Minerva KB admin vs SleekView

Default Minerva KB admin

  • Feedback votes sit in wp_postmeta and don't surface inline
  • No saved view for low-rating or stale articles
  • Category coverage requires manual taxonomy navigation
  • Bulk category reassignment goes one article at a time
  • Vote totals invisible until you open each article

SleekView

  • Pivot helpful, not-helpful, and view counters into columns
  • Filter for articles older than N months across every category
  • Inline-edit category, status, and featured flag
  • Save editorial review views with rating thresholds
  • CSV export of any saved view in one click

Features

What SleekView gives you for Minerva KB

Stale-article view

Filter by last-update older than six months and sort by views descending so high-traffic but outdated articles surface first, where rewrites have the highest deflection impact.

Low-rating triage

Show articles where not-helpful exceeds helpful, sorted by views. The worst-performing high-traffic articles bubble up before they pull down overall deflection.

Inline category edits

Reassign articles to new categories from the list without opening each post. save_post fires so search indexes and sitemaps regenerate as expected.

Audience

Who uses SleekView for Minerva KB

Documentation teams

Audit coverage and find stale articles before they hurt support metrics, with a saved review-cycle view that loads in one click each Monday.

Content ops

Track helpful and not-helpful trends and prioritise rewrites by views-weighted dissatisfaction instead of guessing from category browsing.

Support leads

Spot articles tied to recurring tickets that need clearer answers, then flag them for the docs team with category and rating context attached.

The bigger picture

Why knowledge bases need a real editorial view

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. Minerva KB 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 KB 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.

Questions

Common questions about SleekView for Minerva KB

Yes. Minerva KB writes helpful and not-helpful counters to postmeta each time a reader votes. SleekView reads those keys directly and exposes them as sortable columns. The numbers match what Minerva reports inside each article, same source, surfaced at list level.

 

Yes. Status is a column and edits inline. SleekView triggers save_post so cache layers, search indexes, and sitemap generators all refresh as they would from the post screen. Bulk actions work the same way standard WP bulk edits do.

 

Order is stored in menu_order or a Minerva-specific postmeta key depending on configuration. Make it a column, sort by it, and inline-edit values to rearrange without opening each article. The front-end picks up the new order on the next request.

 

Yes. SleekView writes through standard WordPress APIs so the Minerva-bundled search and any third-party index (SearchWP, FiboSearch, Algolia) update as they would from the post-edit screen. Edits in SleekView trigger the same save_post hooks.

 

Yes. Combine taxonomy filters into a single view. Useful for spotting overlap (an article tagged 'refunds' that's only in 'Security') or coverage gaps where a tag has zero articles in a particular category. Both filters run server-side, so the view stays fast on large KBs.

 

Author is a built-in column. Group or filter by author to track who is writing and updating which articles. Combined with last-updated and views columns, you see which writers are maintaining their work versus which articles are orphaned.

 

If you use a helpdesk that records article references in postmeta or its own table, SleekView can join that count as a column. Articles with high link counts but low helpful ratings are prime rewrite candidates, they're being used as the answer but not solving the problem.

 

Yes. WPML and Polylang store translation links in their own tables. SleekView surfaces language as a column and lets you filter or build per-language views. Helpful for spotting articles where the English version has high views but the translation is stale or missing entirely.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView