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

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

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. A built in rate limit caps how often a single IP can hit the vote endpoint, which keeps public boards honest without forcing a 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 cluster, a score band, a campaign, or any combination of meta fields. Different boards on different pages can use different filters so each editor sees the slice that matters.

The flag is just a category value on the row. You can write it into a meta key NeuronWriter already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the brief, so the SEO lead can act on the flag without leaving WordPress.

They write back to the source column, which means the plugin and your own queries can sort the refresh queue and reports by that score. Several teams use the score to gate which briefs get a rewrite first, which makes the board operational rather than a vanity dashboard.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can 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.

The view paginates server side and only loads rows it needs to render the current page. Indexed columns stay fast even on long tables. For really big projects, scoping the board by cluster or score keeps both the query and the audience focused so the page feels snappy even at scale.