Yes. SleekView reads the Boombox tables and post types directly, so it works whether you run the forum-only setup or the full Boombox theme with reactions on every post type. The reaction rows live in the same table regardless of which content type generated them, so the connector behaves identically.

They do. The Boombox mobile-optimized theme writes to the same wp_boombox_reactions table when a member taps a reaction, so a tap on a phone shows up on the SleekView board on the next render with no extra mapping or sync job. Vote totals stay consistent across desktop and mobile sessions automatically.

Yes. The data source picker accepts a tax_query for category and tag terms, so a Submissions category, a private members-only category, or threads carrying a specific tag can each get a dedicated SleekView board on a separate WordPress page without any custom query code on the theme side.

Status pill updates set the Boombox post tag you mapped to the status column. That is the only write. The thread body, comment chain, and reaction totals stay untouched, so moderators can revert a status by editing the tag and any audit log plugin watching post tags catches the change immediately.

Hidden, pending, and trashed threads drop off the board automatically because SleekView queries only published posts by default. If you want a moderator view that includes pending submissions, the post_status filter accepts an array, so admins can see Pending or Draft rows without exposing them publicly.

No. SleekView paginates the underlying query, caches the sorted set, and only loads the rows needed for the current page. A board with twenty thousand Boombox threads serves in roughly the same time as a board with five hundred because the reaction tally runs once and the cache covers every subsequent visit.

Anonymous voting is off by default because wp_boombox_reactions expects a user ID. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on login, useful for public roadmap pages that catch search engine traffic and shared social links from members.

The SleekView config travels with the source mapping. Repoint the data source picker at the new schema (BuddyBoss, bbPress, or any community tables you can query) and the board renders again. Boombox reaction data stays in its tables until you drop them, so a rollback during a migration window is always possible.