Three levels, because that is the shape a menu already has. Everything is on one screen: sections as blocks, dishes as rows, typed straight into.
Talk to us about your menus →Menu, section, dish. The same three levels every kitchen already uses to talk about its food.
Sections as blocks, dishes as rows. Type into a name or a description, tick a tag, drag to reorder at any level.
One list of tags — a short code and a label — ticked per dish, so the same allergen is never written two ways.
A full menu is a sales asset. Publish a representative sample instead of two hundred dishes, per menu.
A token placed on a page, in a layout or in a template renders the menus, plus two smaller widgets for lighter uses.
The importer recognises menu markup and lifts an existing menus page straight into the tool.
A demonstration installation, with invented data.
Fourteen menus and two hundred dishes published in full reads as overwhelming to a visitor and hands a competitor the whole offer. A per-menu switch publishes a representative sample instead, and the full card stays in the admin for the people who need it.
Dietary information written free-hand per dish drifts within a month: GF, gluten-free, Gluten Free. The tags come from one list, so they are consistent everywhere and can be filtered on.
Menus that change in a minute.
A kitchen changes its menu more often than a business changes its website. The tool has to assume that. Get in touch →
