Menu

How it works

1
Each item contributes a title, a short line and an image if it has one.
2
Tiles reflow to the width available.
3
Selecting one opens the full record.

Best for

Things chosen by eye — products, venues, people.

Not the right choice for

Long lists someone needs to scan quickly.

Who uses this page

Caterer

Quotes the obvious, captures dietary requirements, and never loses a headcount.

Restaurant

Answers the menu, the allergens and the opening hours — in every language your guests speak.

Private chef

Takes the brief — dates, guests, diets, budget — while you are still cooking.

Food truck or street food

Tells people where you are today, and takes the private-hire bookings that pay the rent.

Questions

What data does the Menu page use?

It reads menu_item records the agent has collected. Courses/dishes with options. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a cards the wrong choice?

Long lists someone needs to scan quickly. It is best for: things chosen by eye — products, venues, people.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.