No. SleekView reads the existing property, rental, land, business, and commercial post types and the standard EPL meta keys like property_price, property_status, and property_bedrooms. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the listing data.

Yes. The upvote button supports guest votes with a per IP and per session lock so a single visitor cannot inflate a count. If you would rather restrict votes to logged in users or to specific roles like Agent or Vendor, you can flip that in the view settings without touching theme code.

You map the EPL property_status meta to status values when you build the view. SleekView shows a colored pill for each value, and any listing without a status simply renders without a pill rather than blocking the card. New status values can be added in the view settings as your office vocabulary grows.

Yes. Whether a listing is created in the EPL admin, submitted through a frontend form, or imported via the EPL XML feed importer from a portal sync, it lands in the same post type. SleekView indexes it on the next refresh so the board reflects whatever is currently published.

Yes. Every saved view has its own filter scope, so you can publish a public Sydney board on one page, a Melbourne board on another, and a private Agent Triage view for your sales lead. All of them read from the same property post type without duplicating any records.

When a listing is unpublished or trashed, SleekView removes the card from the public board on the next refresh. The upvote meta stays on the post record itself, so if the property comes back to market, the historic interest score is still there and shows up in EPL exports.

Yes. Every SleekView is available as a Gutenberg block, an Elementor widget, a Bricks element, and a shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so the board can be mounted on any template without touching the page editor.

SleekView paginates and sorts at the database level rather than loading every property post into memory. Indexed meta columns like property_price and property_status stay fast, and scoping a board by suburb, listing type, or status keeps both the query and the buyer audience focused, so the page feels snappy even at portfolio scale.