No. SleekView Feedback reads directly from whatever table or post type Fastor is using, including fastor_cdn_rules and the option keys Fastor populates for purge events. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL job and no duplicated data.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote rules and purges without an account. You can also require login if you want the board restricted to developers 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. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public boards honest without forcing a signup wall in front of your developer audience.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one domain, one path prefix, one rule type, or any combination of fields Fastor already stores. Different boards on different pages can use different filters without duplicating any data.

The Bug category is just a value on the row. You can write it into an option key Fastor already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original rule, so the engineer who wrote the rule can see the flag without leaving WordPress or opening another tab.

They write back to the source column, which means Fastor and any of your own queries can sort future rule changes, retries, and rollbacks by that score. Several teams use the score to gate which rules get promoted to global scope, which makes the board operational and not just 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 at all.

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 really big rule sets, scoping the board by domain or rule type keeps both the query and the audience focused, so the page feels snappy even at scale.