Yes. SleekView reads the Education WP tables directly, so it works whether you use the Education WP theme alone or pair it with the full Education WP plugin suite. The board pulls data from eduwp_reviews, eduwp_quiz_attempts, and eduwp_questions regardless of which add-ons render the front end of the course catalog.

They do. The Education WP mobile reader increments the vote counter through the standard REST endpoint, which writes to the same column the desktop site uses. SleekView Feedback reads from that exact column, so a tap in the mobile reader 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, instructor ID, taxonomy term, or any meta field stored on the question row. A single course, a single instructor, or a curated set of high-signal lessons can each get a dedicated SleekView board on its own WordPress page for the right audience.

Status pill changes update the Education WP question status column you mapped to the status field. That is the only write. The original question text, instructor reply, and review rating stay untouched, so instructors can revert a status by editing the column and any audit log plugin watching the Education WP tables sees the change.

Hidden reviews and rejected questions drop off the board because SleekView queries only visible rows by default. If you want a moderator view that includes pending or hidden items, the query filter accepts a status array so instructors can see them without exposing the rows to enrolled students reading from the public course 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 over fifty thousand Education WP questions 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 Education WP tables independently of enrollment, so a public roadmap page can show course requests, votes, and statuses to prospective students browsing from search. Voting itself can be gated to enrolled students by checking the standard Education WP enrollment meta on submit.

The board keeps rendering as long as the eduwp 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. A migration to a different LMS drops the tables and SleekView falls back to a clear empty state instead of erroring on the page.