Set menu design

Set menus use the same two dedicated designs as tasting menus — Menu design 1 and Menu design 2 — because a set menu is also read as one document. The difference is what those blocks contain: a tasting menu tells, a set menu offers.

What the designs render

  • The menu title and subtitle.
  • The introduction from the description.
  • Each block in order, with its title and the dishes it offers.
  • The footer note.
  • The menu price.

Blocks with no title are not rendered, so a three-course menu uses three blocks.

The dishes come from the pool

Each block's dish selection points at records in Set menu dishes, the separate content type maintained under the Set menu entry. The design renders the selected dishes as the guest's choices for that block.

That is why the same dish can appear in several menus without being copied: it is one record, selected in several places.

Building a menu that lays out well

  • Name the blocks the way a guest chooses: Starters, Main course, Dessert. Not Block 1.
  • Keep the number of choices per block reasonable — three to five. A block with twelve options is a menu, not a choice.
  • Keep the dish names short; they are read as a list of alternatives, not as descriptions.
  • Leave unused blocks completely empty. A titled block with no dishes renders as an empty section.

Supplements

There is no supplement field on a choice. State it where the guest reads the choice:

  • in the block title — Main course (lobster +8€);
  • or in the footer note, when it applies to several options.

Use identical wording wherever a supplement appears.

For a fixed-price menu this is the most important text on the record: VAT treatment, which days and services the menu runs, whether bread and drinks are included, minimum diners, and where allergen information can be requested.

Guests read the price and then the conditions. Write the conditions in the same voice as the rest of the menu.

The daily menu

A menu of the day is usually one permanent record whose dish selections change every morning. The design renders whatever is currently selected, so the guest's URL and QR code never change.

The alternative — one record per day — creates a new address each time and invalidates any printed code. See Set menu.

Allergens

Assign allergens on the dishes in the pool, where the information is precise, and keep a general line in the footer note. The pool is a content type of its own and carries allergen information like any other.

Check it on a phone

  • [ ] Each block's title and its choices are clearly grouped.
  • [ ] The choices are readable as alternatives, not as a run-on list.
  • [ ] Empty blocks are absent, not rendering as gaps.
  • [ ] The price is prominent.
  • [ ] Supplements are visible at the point of choice.
  • [ ] The footer note is legible.
  • [ ] The menu reads correctly in every published language.
Plan a course
Previous
Swipe layout
Next