opentable.com
Design analysis
A recommendation section uses a large featured card beside two compact supporting cards, with category tabs and explanatory editorial copy creating a magazine-like browse experience.
Prompt preview
## Reference images Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language. - Component: https://kage-design-assets.t3.tigrisfiles.io/components/opentable-com/dad68d84-d5d0-4fa5-a1c8-84465fc5fc04-1789146315-3.webp - Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/opentable-com/dad68d84-d5d0-4fa5-a1c8-84465fc5fc04-1789146276379-full.webp - Component on Kage: https://kage.design/component/opentable-feature-grid-2 ## Before you start Ask what the user's product, audience, and brand are, then apply the principles below to that context rather than reproducing a restaurant-booking site. Build an editorial recommendation section with one featured item and a supporting list. Use these rules: - Start with a strong section heading, a small update/date line, one sentence of editorial context, and a simple three-item category tab row. - Use a two-column layout below the tabs: a large horizontal feature card on the left and two compact stacked cards on the right. - The featured card should combine a large image, title, metadata, short summary, rating, save control, and an outlined action. Supporting cards should prioritize thumbnail, title, metadata, and a concise excerpt. - Use white surfaces, #e5e5e5 separators, charcoal typography, and an accent red around #b6384e. Keep corners around 5px and avoid heavy shadows. - Make tabs keyboard navigable with an accent underline for the active tab. On mobile, stack the feature and supporting cards while preserving the editorial hierarchy. Never: use logos, product names, copy, illustrations, imagery, or exact visual assets from the reference.
kage