No. SleekView reads existing wp_block posts, Cwicly block references inside serialized post_content, and the postmeta values that the block editor already writes. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the pattern data.

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 Designer, you can flip that in the view settings without touching any code at all.

You map a cw_review_status meta key on the wp_block post when you build the view. SleekView shows a colored pill for each value, and any pattern 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 block editor has registered. Reusable blocks, frame templates, global classes, and individual saved patterns all surface as cards on the board, grouped by the family chip you pick during view setup without any special configuration step at all.

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

When the underlying wp_block post is deleted, SleekView removes the card on the next refresh. If the pattern is trashed rather than fully deleted, the card disappears from the public view but the upvote meta is preserved on the trashed post in case you restore it later from trash.

Yes. Every SleekView is available as a shortcode, a Gutenberg block, and a block editor wrapper. You can drop a Needs refactor view onto a Design Ops page, embed a Top usage view on a planning wiki, or stitch several views into a single dashboard with separate columns side by side.

SleekView paginates and sorts at the database level rather than loading every wp_block into memory, so a site with hundreds of Cwicly patterns and reusable blocks still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.