All work · Live

Ō Lounge

A hotel lounge replaces printed menus with a photo-led Food and Drinks menu, opened from one QR code. Staff update dishes, prices, availability and photos themselves.

Ō Lounge, Romance Alexandria Hotel · Egypt · Alexandria

The live menu ↗
Client
Ō Lounge, Romance Alexandria Hotel
Region
Egypt · Alexandria
Status
Live
Delivery
Whisky 11

The problem and context

A hotel lounge needs a menu that feels like its brand and is easy to browse at the table. One QR code replaces separate printed lists while staff control the content.

Who uses it

  • Guests at Ō Lounge in the Romance Alexandria Hotel
  • Lounge staff maintaining Food and Drinks menus

What was built

  • Food and Drinks menus with category photography and house signatures
  • One QR code, menu switching and continuous category browsing
  • Staff admin for dishes, categories, prices, sold-out states and photo uploads
  • Photos optimised at upload and stored in R2
  • Server-rendered pages and CSS interactions without first-party client JavaScript

How it works

  1. Guest scans the venue QR and chooses Food or Drinks.
  2. House signatures and photographic category cards guide browsing.
  3. Opening a category starts continuous menu scrolling, with sticky navigation to the next category.
  4. Staff sign in to edit categories, items, prices, photos, visibility and sold-out states.

How the system fits together

  • Hono renders JSX on one Cloudflare Worker; the interaction model uses links and CSS rather than first-party client JavaScript.
  • Cloudflare D1 stores menu records; R2 stores dish and category photos.
  • Cloudflare Images optimises uploaded photos, with validated-original fallback if optimisation fails.
  • Server-side validation and login rate limiting guard the staff interface.

Technology stack

  • Hono + TypeScript
  • Server-rendered JSX
  • Cloudflare Workers
  • Cloudflare D1
  • Cloudflare R2 + Images
  • Zod

Delivery and current status

  • Live menu linked at olounge.whisky11.com.
  • Food and Drinks are separate menus behind a single venue QR.
  • The initial Food catalogue comes from the client’s agreed menu PDFs; staff can update it without a developer.

Evidence

  • Live at olounge.whisky11.com
  • 137 food dishes across 13 categories, plus a separate Drinks menu
  • Food dishes can remain visible without a price until staff price them

Scope and operating limits

  • The menu is English-only and uses EGP; it is a browsing menu, not a payment or order-checkout system.
  • Food items may display without a price until the owner provides one.
  • Illustrative placeholder photography is disclosed on the menu until replaced with real venue photos.

← All work · Start a project