No. SleekView reads the existing et_pb_layout library items, the nav menu term meta bindings that Divi Mega Pro writes, and the wp_postmeta values that Divi already keeps. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the library 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 Marketer, you can flip that in the view settings without touching any code or menu permissions.

You map a dmp_review_status meta key on the library item 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.

Yes. SleekView reads whatever Divi has registered. Desktop mega menus, mobile-only variants, and responsive overrides all show up as standard et_pb_layout records and the board surfaces them alongside each other without any special configuration on your part.

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 Nav Refactor queue that only Navigation Editors and Admins can see. Both views share the same library data.

When the underlying et_pb_layout library item 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.

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 Nav Ops page, embed a Top usage view on a planning wiki, or stitch several views into a single dashboard with separate columns.

SleekView paginates and sorts at the database level rather than loading every library item into memory, so a site with dozens of mega menus and hundreds of menu bindings still renders the top of the feedback board in well under a second on a normal shared host.