AIT Restaurant Menu builds the menu around a custom post type for dishes, with prices, categories, dietary flags, and descriptions stored as postmeta on each item. The default WP admin shows the menu items as a post list with title and date, which is not how a restaurant updates a daily menu.

SleekView reads the menu CPT and joins the relevant wp_postmeta rows. Price, category, dietary flags (vegetarian, vegan, gluten-free), allergens, and availability surface as columns. Filters compose, so a manager can build a view of Vegetarian mains under 15 in one click. Saved views per restaurant location let multi-site groups manage each menu independently.

Inline edits route through AIT's normal save paths. A price change updates the front-end menu instantly. An availability toggle hides a dish from public view exactly as the plugin's own edit screen would. SleekView is admin-only and never re-implements the menu templates.

A restaurant menu is operationally different from a blog. Prices change with the season, dishes sell out mid-service, and special dietary requests shape the day. The default WP admin treats menu items like blog posts and surfaces title and date in a flat list.

Managers end up opening every dish to update a price or hide an item that has just sold out. Multi-location operators face the same problem multiplied: each location's menu mixes into one giant list with no filter. The data is in wp_postmeta, sitting there, indexed and queryable.

SleekView gives operators a service-ready grid over data that already exists. AIT's front-end menu templates and any theme integration keep working through their normal paths. The admin just starts moving as fast as the kitchen does.