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

Yes. SleekView ships with anonymous voting backed by cookies, so public readers can upvote issues without an account. You can also require login if you want the board restricted to paying subscribers, 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. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public archives 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 a particular tag, status, or date range Buttondown already tracks. Different boards on different pages can use different filters, which makes per topic archives easy.

Bug is just a category value on the row. You can write it into a meta key Buttondown already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original issue, so the editor can see the flag without leaving WordPress or opening Buttondown.

They write back to the source column, which means Buttondown and any of your own queries can sort future issues and tags by that score. Several writers use the score to gate which topics get a part two and which ones get quietly archived, making the board an editorial input 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 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.

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