bbPress stores topics as the topic post type and replies as the reply post type, both inside wp_posts, both using the standard WordPress post_status column plus the bbPress-specific values spam and closed. The built-in screen is the same edit list that powers every other post type, which is fine for editorial work but slow for forum triage where a moderator needs to see all open threads, all reported threads, and all spam in the same view.

SleekView Kanban reads wp_posts filtered by the bbPress post types, groups rows by the post_status value, and renders one card per topic. Each card carries the forum name from the parent topic, the reply count from _bbp_reply_count, the voice count, the last reply author, and the time since the last reply, so a moderator can decide at a glance whether to answer, close, or spam the card.

Dragging a card from Open to Closed calls bbp_close_topic(), from Open to Spam calls bbp_spam_topic(), and the reverse drags call the matching unspam and reopen functions. Notifications, counts, and last-active timestamps update through the standard hooks, so the board stays in sync with the forum itself and with any custom code already listening for those events.

Forums have a rhythm. Topics open, reach a peak in the first day or two, and then either close cleanly with an answer or drift into silence with no resolution. Spam shows up at the edges, sometimes in waves, and trash is the resting place for tests, duplicates, and posts that were never quite right.

The default bbPress admin treats every one of those rows as the same kind of object, which is correct but unhelpful, because the work of moderation is precisely about treating them differently. A kanban board makes the difference visible. The Open column is the live forum, the Closed column is the recent history, the Spam column is the cleanup task, and the Trash column is the audit trail of what was removed.

Moving a card is no longer a row action buried behind a hover state. It is the moderation itself, the same shape as the work. That clarity is why support teams ship more answered threads per week with a board, why volunteer moderators stay around longer because the board lowers the cost of showing up for ten minutes, and why announcement forums feel cared for rather than stale.

The bbPress data has always been ready for this view, SleekView Kanban just makes it the default.