Directorist uses a custom post type at_biz_dir for businesses with a long list of meta keys such as _address, _phone, _email, _listing_status, and a built-in featured flag. It also exposes its own review storage so customers can rate each entry. The default admin is a list table and the default frontend is a search and grid layout, neither of which surfaces a single ranked feedback view across the whole directory.

SleekView reads the at_biz_dir records and their meta, then renders one feedback card per listing. The vote score can pull from the rating, review count, or a custom meta value, the status pill maps to _listing_status or the featured flag, and the category chip uses the standard Directorist category taxonomy. Visitors interact with the board through familiar Upvote buttons that increment a meta value on each post.

The standard Directorist frontend keeps rendering through its existing templates and the admin tools remain untouched. SleekView only adds a ranked review surface on top of the same data, so moderators get a triage queue, visitors get a Product Hunt style board for the directory, and the listing meta keeps acting as the single source of truth for every score and status.

Directorist gives you a powerful schema for listing data, but a busy directory accumulates problems faster than any single moderator can fix them. Outdated phone numbers, broken contact forms, fake premium listings, and closed businesses still showing as Verified all hurt visitor trust. The standard Directorist admin lets one person triage one listing at a time, and visitors have no structured way to flag issues short of filing a support ticket.

SleekView gives the same at_biz_dir data a vote-driven home. Visitors get a ranked board where they can upvote listings worth fixing or boosting, and moderators get saved views that surface the highest priority items first. Because the score lives in standard post meta, it shows up in Directorist exports, in any reporting tool that reads at_biz_dir, and in custom dashboards built by the development team.

The directory becomes a feedback loop instead of a static catalogue.