No. SleekView reads existing cs_global_block and cs_template posts, the serialized Cornerstone trees inside post content, and the postmeta values that Cornerstone already writes. The only write is the upvote increment, which lands on a meta key you choose so it sits with the rest of the section 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 cs_review_status meta key on the Cornerstone global block or template when you build the view. SleekView shows a colored pill for each value, and any section without a status simply renders without a pill rather than blocking the card from showing on the board at all.

Yes. SleekView reads whatever Cornerstone has registered. Global blocks, Pro headers, Pro footers, and individual saved templates all surface as cards on the board, grouped by the type 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 Cornerstone Refactor queue that only Designers and Admins can see. Both views share the same data underneath.

When the underlying cs_global_block or cs_template post is deleted, SleekView removes the card on the next refresh. If the section 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.

Yes. Every SleekView is available as a shortcode, a Gutenberg block, and a Cornerstone element wrapper. You can drop a Needs refactor view onto a Design Ops page, embed a Top reuse 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 Cornerstone post into memory, so a site with hundreds of cs_global_block and cs_template records still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.