No. SleekView only reads the mn_post CPT that Mighty Networks Bridge syncs into WordPress, along with the postmeta values the sync writes. The only write inside WordPress is the upvote increment, and any status pill edit is mirrored back into Mighty by the next Bridge sync without touching the platform directly.

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 Host, you can flip that in the view settings without touching any code on the WordPress site.

You map a mn_review_status meta key on the mn_post entries when you build the view. SleekView shows a colored pill for each value, and any post 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 Mighty Networks Bridge has registered. Multiple hosts, topics, and even archived hosts can be filtered into separate saved views, so a marketing page can show one host 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 Host Triage queue that only Hosts and Admins can see. Both views share the same Mighty data underneath.

When the underlying mn_post record is deleted by the next sync, SleekView removes the card. If the post 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 later down the road.

SleekView itself lives in WordPress, but the saved views render as shortcodes, Gutenberg blocks, and iframes. Many teams embed a Top reactions board inside Mighty using a third-party iframe block on a host welcome page so members see the WordPress roadmap without leaving Mighty at all.

SleekView paginates and sorts at the database level rather than loading every mn_post into memory, so a sync history with thousands of synced posts still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled today.