Meraki

The problem

A landing page has one shot: one screen, one scroll, no second page to redeem a bad first impression. And a pattern shows up constantly in real inquiries — most people who reach out don't have a menu written, photos taken, or copy ready yet, and that shouldn't be what stands between them and seeing what's possible.

The approach

I built this with zero client input — no brief, no menu, no photography — specifically to prove that isn't a blocker. The whole page borrows its structure from a Greek coffee-cup fortune ritual: pour, wait, reveal, with each dish introduced the way a fortune-teller reads a cup instead of a category label. I wrote it fully trilingual from day one — German by default for the real target customer, with English and Greek as genuine, separately-authored options rather than a machine-translated afterthought.

What came out of it

• →Went from a blank page to a finished, trilingual site with zero content, photography, or brief provided — proof the Landing package doesn't need a client to be ready first
• →German by default, with English and Greek written as real, separately-authored options — not machine translation bolted on afterward
• →An honest trade-off, stated plainly: I chose memorable over fastest-to-skim, and leaned on type and color because there was nothing to photograph — real photography is still what most restaurant clients will actually want