It works alongside them. SleekView reads from the same wp_comments rows LearnDash already writes, so existing ratings still appear under each lesson and inside the LearnDash reports. The board is an additional public view of the same data with upvotes layered on top, not a replacement, and disabling the board never affects the ratings already collected.

Upvotes are stored in a custom column SleekView adds on install, or in a meta key on the existing comment or post row. You pick the location during setup. Most LearnDash sites use the meta key path because it survives plugin updates cleanly, and it stays inside the standard WordPress meta tables that your existing exports and reporting tools already understand.

You decide. SleekView ships with three voting modes, logged-in only, logged-in with rate limit, and anonymous with a per-device cookie. Course sites that gate content usually pick logged-in only, which uses the LearnDash session so only enrolled users vote. Free preview boards on marketing pages often pick the cookie mode to lower the friction.

Yes. The board reads through the same access control filters LearnDash applies to its own queries, so private groups, drip-fed lessons, and prerequisite-gated content never leak. If a student cannot see a lesson inside LearnDash, the feedback card linked to that lesson is hidden from their board view, even though it still exists for instructors and admins on the back end.

SleekView adds an optional status meta key during install, defaulting to Open. Instructors set the status from the admin board or via WP-CLI, and it renders as a colored pill on every card. Color comes from the value itself, mapped through a small theme file you can edit. Sites with an existing project management plugin can map the status column at any custom field they already populate.

No. SleekView paginates by default, caches the visible page for sixty seconds, and runs the upvote write as a single indexed update. The query reads the same indexed columns LearnDash uses for its own reports, so even a course library with fifty thousand comments renders the board in under a second on standard managed WordPress hosting without any extra caching layer.

Yes. The shortcode and block both accept a course filter, a group filter, and a category filter. You can place a board scoped to a single LearnDash course inside that course page, a board scoped to a group of related courses on a cohort dashboard, and a global board on the marketing page, all reading from the same underlying data with no duplication.

Nothing is lost. SleekView never deletes LearnDash comments, ratings, or quiz reports. Removing the plugin drops the board UI and the upvote write hook, but the underlying rows stay in wp_comments and wp_learndash_user_activity, exactly as LearnDash wrote them. Reinstalling later picks up the same rows and the same vote counts you collected before, with no data import required.