No. SleekView reads the existing et_pb_layout posts, the Divi module shortcodes inside page content, and the wp_postmeta values that Divi 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 layout 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 db_review_status meta key on the layout post when you build the view. SleekView shows a colored pill for each value, and any layout 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 Divi has registered. Theme Builder headers, footers, body templates, and global presets all show up as et_pb_layout records and the board surfaces them alongside individual page layouts 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 Design Refactor queue that only Designers and Admins can see. Both views share the same data underneath.

When the underlying et_pb_layout post is deleted, SleekView removes the card on the next refresh. If the layout 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 Divi module 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 et_pb_layout into memory, so a site with hundreds of Divi Builder layouts still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled.