Yes. SleekView reads the Courses Vibe tables directly, so it works under any theme that the Courses Vibe plugin supports, including the bundled pro theme. The board pulls data from cv_suggestions, cv_reviews, and cv_lessons regardless of which theme renders the public course catalog or the lesson player on the front end.

They do. The Courses Vibe student app increments the suggestion vote counter through the standard REST endpoint, which writes to the same column the desktop site uses. SleekView Feedback reads from that exact counter, so a tap in the app shows up on the board on the next render and counts toward the sort order.

Yes. The data source picker lets you filter the underlying query by course ID, lesson ID, tag value, or any meta field stored on the suggestion row. A single course, a single lesson, or a curated set of high-signal suggestions can each get a dedicated SleekView board on its own WordPress page for the right student audience.

Status pill changes update the Courses Vibe suggestion status column you mapped to the status field. That is the only write. The original suggestion text, vote counter, and student identity stay untouched, so instructors can revert a status by editing the column and any audit log plugin watching cv_suggestions sees the change.

Rejected suggestions and hidden reviews drop off the board because SleekView queries only visible rows by default. If you want a moderator view that includes pending, hidden, or rejected rows, the query filter accepts a status array, so instructors can triage them without exposing the rows to enrolled students on the page.

No. SleekView paginates the underlying query, caches the sorted set per page slug, and only fetches the rows it needs for the current page. A board with over fifty thousand Courses Vibe suggestions serves in the same time as a board with five hundred because the database does the heavy lifting once and the cache covers every subsequent visitor.

Yes. The board reads from the Courses Vibe tables independently of enrollment, so a public roadmap page can show lesson suggestions, votes, and statuses to prospective students. Voting itself can be gated to enrolled students by checking the standard Courses Vibe enrollment meta on the submit handler.

The board keeps rendering as long as the cv tables exist in the database. Deactivating the plugin freezes the data at the last write, so the board still serves with stale counts until reactivation. Migrating to a different LMS drops the tables and SleekView falls back to a clear empty state instead of erroring on the public page.