SleekView groups by the review_status taxonomy, the same field KB Suite uses for the editorial workflow. You can also group by author, by category, or by assigned reviewer to switch between an editorial view and a per-person workload view.

Yes. When the target stage is Published, SleekView calls wp_publish_post in addition to writing the review_status term, so the article hits the public KB the moment the editor approves it on the board, without a second click in the editor.

Yes. The feedback score from wp_kbsuite_feedback renders as a numeric badge on the card. Sort within a column by feedback descending and the highest-rated drafts or lowest-rated published articles float to the top of the relevant column quickly.

Because SleekView writes through KB Suite's REST endpoint, the audit log records the editor who dragged the card, the source stage, the target stage, and the timestamp. The audit trail matches what the article edit screen produces for a manual change.

Yes. Writers load a board grouped by review_status filtered to their own author meta. Managers load a board grouped by reviewer to balance load. The underlying kbsuite_article dataset is shared so changes from one view appear instantly in the other.

Yes. Filter the board by kbsuite_category to focus on one product area, save the filter as a named board, and reload it next week. Each board keeps its columns, filters, card fields, and color palette so the editorial workflow stays consistent.

Yes. Select multiple cards in the Published column, drag them in one motion to the Archived column, and SleekView writes the review_status change through the REST endpoint for every selected article. The audit log records each change individually.

SleekView polls for changes at a configurable interval, defaulting to thirty seconds. Updated drafts appear with a brief highlight on their card, last-edit dates refresh, and the column counts update so the manager sees the pipeline move.