Fider WP brings community feedback boards to WordPress in the spirit of the open-source Fider project. Each post is a CPT row; vote count and category live on postmeta, and discussion uses standard wp_comments. The public board sorts by votes, the Posts screen lists submissions with no status or comment columns, and the moderator team has no per-row queue with the data they actually need.

SleekView reads the Fider WP CPT, the vote meta, and the wp_comments join inline. Title, status, category, vote count, comment count, author, and submission date sit as proper columns. Sort by comments to surface the most-discussed posts, filter to status=Started on a single category, or scope to high-vote posts that have no admin reply yet.

The plugin keeps owning the public board, the voting endpoint, and the submission flow. The table view becomes the moderation surface, so triage stops meaning a column-by-column scroll and starts meaning a saved query.

Fider WP gives a community a public place to file feedback and vote on it, modeled on the original Fider experience. The product team running the board needs the same data through a different surface. They need to triage by status on one category, surface the most-discussed posts, find votes above a threshold, or pull a per-author rollup before a roadmap review.

The public board cannot do that, and the Posts screen treats each post as a flat row. SleekView reads the same feedback CPT, vote meta, and comment data the board already produces, then renders the result as a queryable admin grid. The plugin keeps owning the visitor experience, while the team gets the per-row table that triage actually requires.