Yes. SleekView reads the same wp_terms and wp_term_taxonomy tables Metronet uses, then filters by a meta key that identifies reader submissions. You can show only reader-submitted tags on the board, only editor-created tags, or both in separate boards depending on the workflow your team prefers for moderation.

Yes. Each card has an editor-only side panel with Approve and Decline buttons that update the moderation state meta key directly. The status pill on the card changes immediately, the tag stays on the board for context, and any submission count or upvote total remains visible for post-decision analysis.

You choose the weight per signal in the SleekView view config. A common setup is one point per Metronet submission plus two points per SleekView upvote, but you can also use upvotes only, submissions only, or any other weighted combination that matches how your team thinks about reader interest in a candidate tag.

Yes. A SleekView block can scope itself to a moderation state filter, so a public Pending board only shows tags still under review. Editors keep a separate internal board that includes Approved and Declined tags for context, while readers stay focused on the proposals that still need their input.

Yes. SleekView reads any taxonomy Metronet Tag Manager is configured for, so custom taxonomies like ingredient, mood, or skill level all work the same way as standard post tags. You pick which taxonomy a board scopes to, and the cards render with that taxonomy's specific moderation rules and meta keys.

Yes. The submitter ID is exposed as a column from termmeta, so the board can filter by author, group by author, or show a per-author leaderboard for proposals. That makes it easy to recognize the writers whose tag suggestions land most often and to spot patterns in what each author tends to propose.

Yes. The SleekView toolbar includes a CSV export that respects the current filter, so you can pull every Pending tag from the last thirty days, every Approved tag from a specific taxonomy, or any other slice into a spreadsheet in one click for offline review and discussion.

Yes. SleekView never owns Metronet data, it only reads from and writes to the same termmeta keys Metronet already manages. Removing SleekView leaves every submission count, moderation state, and tag intact, so the default Metronet admin keeps working with no rebuild or data migration step required.