BuddyPress Docs stores collaborative wiki-style documents as the bp_doc custom post type, with group assignment via a taxonomy, access settings in postmeta and edit history through standard WordPress revisions. The default surface is a per-group doc list and a sitewide directory, which is right for finding a doc and wrong for understanding how the wiki is actually used at the cohort level.

SleekView reads wp_posts filtered to post_type=bp_doc, joined with wp_postmeta for access settings, the BP Docs group taxonomy and wp_users for display_name. Each doc is one row with title, group, author, access setting and post_modified as real columns. Filter to a group to scope a quarterly review. Sort by post_modified to find docs going stale. Filter by author to recognise editors who maintain the wiki.

BuddyPress Docs keeps owning editing, revision tracking and front-end rendering. The table view owns the audit surface, so the docs bp_doc already maintains stop hiding behind per-group lists and become something knowledge managers and group leaders can actually query.

BuddyPress Docs captures something genuinely useful: collaborative wiki-style documents assigned to groups, edited over time and tracked through standard WordPress revisions. The default surface tucks that signal into per-group doc lists, which is right for finding a doc and wrong for understanding the wiki at the cohort level. SleekView reads the same bp_doc posts and renders them as a queryable audit table with group, author, access setting and last-edited date as real columns.

Filters stack into a single query so the group review, the stale-doc audit and the editor-recognition shortlist become one-click saved views. BuddyPress Docs keeps owning editing, revisions and access enforcement, while group leaders and knowledge managers get the per-row surface the dataset always deserved.