No. SleekView Feedback reads directly from whatever table or post type Surfer is syncing into. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. There is no ETL job, no sync, and no duplicated data. Anything Surfer writes shows up on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote drafts without an account. You can also require login if you want the board restricted to editors or paying clients, and the same view handles both modes with a single setting toggle in the WordPress admin.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by user ID. The plugin also exposes a per IP rate limit so a single visitor cannot spam the board, which is enough to keep public boards honest without forcing a full signup wall in front of casual readers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one project, one language, or any combination of meta fields Surfer already syncs into WordPress. Different boards on different pages can use different filters with no extra plugin setup at all.

Audit feedback is just a category value on the row. You can write it into a meta key Surfer already understands or a dedicated column. Either way it shows up in the WordPress admin next to the original draft, so the writer who owns the article can see the flag without leaving WordPress or hopping back into the Surfer dashboard.

They write back to the source column in WordPress, which any of your own queries and reports can read. Several teams use the score to gate which drafts get re audited at all, which makes the board operational and not just a vanity dashboard you show clients once a quarter on a review call.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any template without touching the page editor or the block library at all.

The view paginates on the server and only loads the rows it needs to render the current page. Indexed columns stay fast even on long tables. For really big projects, scoping the board by language or content type keeps both the query and the audience focused, so the page stays snappy even at scale with thousands of stored drafts.