The menu to organise
Imagine a cafe that supplies separate morning and later menus. Some drinks appear on both, while several dishes belong to only one selection. The first design question is how a reader should understand those groups without having to compare two dense documents.
The cafe would need to confirm the content and any service-time wording. Those facts belong to the restaurant. The design can give them a clear place, but it should not infer availability from the way a previous menu happened to be arranged.
An approach to the page
One possible layout begins with a choice between the two approved selections and keeps drinks easy to reach from either. Each section uses consistent item spacing, a readable description style and prices that stay close to the correct dish.
The selected menu is clearly labelled. A short piece of approved context can explain the selection where needed. On a phone, the navigation stays compact and the menu reads as a single column, with enough room for longer names and descriptions.
What the review would cover
The cafe would review the complete content in the proposed layout, including the longest dish names and any shared items. The design review would check how the selection changes and whether the reader can find the other menu without losing context.
What this example shows
This is a hypothetical layout exercise, not a client case. It makes no claim about ordering behaviour or restaurant performance. The purpose is to show how a menu structure can respond to the actual content the business supplies, with the same decisions carried through the wide and narrow versions of the page.