No. SleekView reads the existing elementor_library posts, JetElements widget references inside _elementor_data, and the postmeta values that Elementor 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 template 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 on the site.

You map a je_review_status meta key on the Elementor template when you build the view. SleekView shows a colored pill for each value, and any widget without a status simply renders without a pill rather than blocking the card from showing on the board at all.

Yes. SleekView reads whatever Elementor has registered. Popups, header templates, footer templates, theme builder parts, and individual saved templates all surface as cards on the board, grouped by the family chip you pick during view setup without any special configuration.

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 JetElements Refactor queue that only Designers and Admins can see. Both views share the same data underneath.

When the underlying elementor_library post is deleted, SleekView removes the card on the next refresh. If the template 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 an Elementor widget 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 elementor_library into memory, so a site with hundreds of Elementor templates referencing JetElements widgets still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.