SleekView Kanban for Minerva KB
SleekView reads the Minerva KB article tables directly, groups every article by its workflow state, and lets the docs team drag cards across Draft, In review, Published, Archived so the underlying record updates the moment the column changes.
♾️ Lifetime License available
Why Minerva KB fits a kanban view
Minerva KB stores each article in wp_posts for the minerva_article post type with metadata in wp_postmeta for icon and order fields. Each row has an ID, a created timestamp, an author, a category tag, a workflow state, and the article body rendered to readers on the frontend knowledge base. The default Minerva admin lists articles in a paginated screen, fine for occasional editing and weak when a Minerva KB documentation lead needs to coordinate a content sprint across dozens of articles that all need a documented review.
SleekView Kanban reads the same wp_posts for the minerva_article post type rows the Minerva admin queries. Pick the workflow state field as the grouping column and every entry becomes a card under Draft, In review, Published, Archived. Card fronts can show the author, the category, the reviewer, the last update timestamp, and the word count so the docs lead can prioritize the publishing queue from a single board.
Dragging a card writes the new workflow state back to the Minerva record. A move from In review to Published flips the post status and timestamps the action. The plugin's hooks for category updates, search reindex, and analytics keep firing, so a manual move never breaks the live knowledge base index or the analytics pipeline that reports article health.
Workflow
From Minerva list to a live documentation board
Connect Minerva as a source
Pick the workflow column
Choose card front fields
Enable drag-and-drop writeback
Sample board
Sample Minerva editorial review board
Comparison
Default Minerva article list vs SleekView Kanban
Default Minerva KB list
- Long article list with no review queue showing what is still pending
- Filtering by category reloads the page and loses the author filter set
- No visual sense of which articles are in review versus already live
- Marking an article published needs the per-row context menu and dialog
- Coordinating a content sprint needs editor rights and Minerva training
SleekView Kanban
-
Reads directly from
wp_postsfor the minerva_article post type andwp_postme - Drag a card to Published and the Minerva post status writes atomically
- Cards show author, category, reviewer, last update, and word count
- Column counts update live so a backlog of drafts surfaces instantly
-
Per-role caps tie writeback to
edit_postsfor the docs team
Features
What SleekView Kanban gives you for Minerva KB
Native Minerva model
Every column maps to a real workflow state stored in the Minerva record. Category updates, search reindex, and analytics hooks keep firing for new articles, so a manual review move never breaks the live knowledge base index or dow
Drag-and-drop with trail
Each move writes a state change into the Minerva record naming the editor who dragged it, the source column, the destination column, and the timestamp. If a lead pushes an article back from Published to In review, the chain stays
Saved board views per sprint
Filter to one category for the on-call writer, drafts older than seven days for the editor, and articles awaiting screenshots for the docs lead. Each saved view becomes a shareable URL that opens the right board for each editor.
Audience
Where a Minerva kanban changes editorial work
Weekly editorial sprint
Docs leads scope the board to this week's drafts, drag articles into In review, and confirm Published only when an editor has signed off. The next sprint starts with a board that already shows exactly
Stale draft cleanup
Editors filter to drafts older than thirty days, move stalled cards into In review for a recovery pass, and archive the truly dead ones so the active board reflects only articles a writer is actually
Reviewer load balancing
Team leads scope to one reviewer's queue, see how many articles are pending review versus already cleared, and reassign work so no reviewer ends the sprint with twice the workload of the rest of the t
The bigger picture
Why this view matters for Minerva editorial work
Minerva KB captures every article, which is exactly what makes the default admin list hard to use across a docs team. The sortable list is fine when an editor knows what they want and almost useless when a Minerva KB documentation lead needs to coordinate a sprint across articles that all need a documented review and a publish decision. Most teams export a CSV, drop it into a sheet, and tag articles by hand.
The sheet drifts within a day. New articles keep landing in Minerva without a workflow tag, the sheet records publish dates that nobody copies back, and by the end of the week the two views disagree on what is still pending review. A kanban view that reads and writes the same Minerva record as the admin keeps the docs team and the source of truth aligned.
Draft cards surface immediately. In review cards stay visible across reviewers. Published articles carry a documented sign-off and a named editor, all without leaving WordPress.
Questions
Common questions about SleekView Kanban for Minerva KB
Live. SleekView queries the same wp_posts for the minerva_article post type and wp_postmeta for icon and order fields rows the Minerva admin reads. Filters apply at the SQL level, so a board scoped to this sprint reflects articles that landed in this sprint, not a snapshot exported earlier this week.
No. SleekView writes the new workflow state into the Minerva record. Category hooks, search reindex, and analytics keep operating on the original record, so a card move never re-fires a publish event, never suppresses one, and never alters analytics already logged.
Yes. The category, author, and last update fields live on every Minerva row. SleekView exposes all of them as filters and board grouping options, so a docs lead can scope to one category, to one author, or to articles untouched for thirty days for a recovery pass.
Yes. Every move runs through current_user_can('edit_posts') and the Minerva editor capability before any record write. A contributor account can drag for personal sorting but the change does not persist, with a toast notification explaining why the move was rejected.
Filters apply at the database query level rather than in JavaScript. A typical board scopes to this sprint, to one category, or to drafts only, so the rendered card count stays well under a thousand. Older articles remain queryable in archive views without slowing the live board.
Yes. The last update timestamp lives on every Minerva row and the word count is derived from the article body or its meta. SleekView exposes both as card fields, so an editor can spot stale drafts across articles and queue them for a refresh without clicking into each one.
Yes. Premium add-ons attach analytics, feedback votes, and search data to every article. SleekView reads the same record fields, so premium signals like vote count, feedback ratings, and view counts continue to surface on each card while the board reflects state changes.
Yes. Every drag writes a state change entry into the Minerva record naming the editor, source column, destination column, and timestamp. The entry uses the Minerva metadata API so audits, exports, and downstream automations read the trail without a separate review log.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout