No. SleekView reads the muut_topic CPT that the Muut WordPress sync mirrors locally, and any upvote increment lands on a WordPress postmeta key. Status pill edits update the same postmeta key, which the Muut WordPress sync can choose to mirror back into a Muut tag during the next refresh cycle.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or specific roles like Editor or Moderator, you can flip that in the view settings without touching any code at all.

You map a muut_review_status meta key on the muut_topic entries when you build the view. SleekView shows a colored pill for each value, and any topic without a status simply renders without a pill rather than blocking the card from showing on the board at all in public.

Yes. SleekView reads whatever the Muut sync has mirrored. Multiple forum paths, archived paths, and per-language paths can be filtered into separate saved views, so a marketing page can show one path and a support page can show another without conflicting category chips at all.

Yes. Every saved view has its own role and capability scope, so you can publish a public Community Ops feedback wall on an editorial page and a separate Moderator Triage queue that only Moderators and Admins can see. Both views share the same Muut data underneath.

When the underlying muut_topic record is removed by the next sync, SleekView removes the card on the next refresh. If the topic is archived rather than deleted, the card disappears from the public view but the upvote meta is preserved on the archived row for export and history purposes.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most teams drop a Top likes view above or beside the Muut widget on the same community page so the upvote board and the native chronological view share the page without conflict.

SleekView paginates and sorts at the database level rather than loading every muut_topic into memory, so a sync history with thousands of topics across many forum paths still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.