A Café Website, Not a Template
Story-first hospitality website with a rotating menu, live in three weeks
A Copenhagen specialty café wanted its slow-morning philosophy felt before anyone walked in. We built the site around the story, not a menu PDF.
What the café needed
The café runs on simple rules: real ingredients, house-roasted beans, no rushed mornings. Restaurant builders push the same hero photo, menu grid and map link every competitor uses. The owner wanted a site that reads like a short magazine feature, with a seasonal menu they can change without a developer. We ran it as a fixed-scope build. One focused homepage carries the story and the signature bowls, with two actions: view the menu, visit the café. An image pipeline keeps the editorial look fast. Brand direction to live: three weeks.
Constraints we had to design around
- 01
The most templated category on the web
Café and brunch sites mostly share one layout. Standing out meant dropping the default hero-plus-menu-grid structure entirely.
- 02
Photography carries the sale
There is no long sales copy for a café. The bowls and the interior had to persuade on their own, so image quality and image speed both mattered.
- 03
Editorial look, light pages
Large photos and serif display type can make a site feel slow. The design had to stay fast on mobile despite being image-led.
- 04
A menu that changes every season
Signature bowls rotate. The structure had to present the current menu clearly without implying it is permanent, and without a rebuild each season.
Architecture and what we shipped
- 01
Story before menu
The homepage opens with the café's own words, why it exists and what it refuses to compromise on, before it shows a single bowl.
- 02
Editorial layout system
Serif display type, generous whitespace and an asymmetric photo layout give a magazine feel that matches a slow, craft-led brand.
- 03
Menu as a seasonal feature
Signature bowls sit in a seasonal block with a note that the lineup rotates. The owner swaps content, the structure stays.
- 04
Image pipeline
Every photo converted to WebP and served at responsive sizes through Next.js Image, so the photography loads fast on a phone.
- 05
Two actions, always visible
"View Menu" and "Visit Café" are the only primary actions on the homepage. Short path from browsing to walking in.
Three weeks, direction to live
One week for direction and copy, one for design and build, one for QA and launch.
-
Week 1
Direction and content
Brand tone, page structure and story copywriting
-
Week 2
Design and build
Editorial layout, photography treatment and component build
-
Week 3
QA and launch
Image optimisation, cross-device checks and go-live
What shipped
From brand direction to a fully live café website
Brand story, philosophy and rotating menu on one focused homepage
Every photograph optimised and served responsively for fast mobile loading
Questions restaurant owners ask us
Can you build a restaurant website that doesn't look like a template?
Yes. This café site leads with the brand story and editorial photography instead of the usual hero image and menu grid. That single structural decision is what separates it from the rest of a heavily templated category.
How do you keep a photo-heavy restaurant site fast?
Every image is converted to WebP and served at responsive sizes through Next.js Image. Large food and interior photography stays sharp without slowing the site down on mobile.
Can we update a seasonal menu ourselves?
Yes. The menu is structured as a seasonal feature rather than a fixed list, so the café changes its signature bowls without structural changes to the site.
How long does a café or small restaurant website take?
This one took three weeks from direction to launch as a focused, single-page-led site. Ordering, reservations or several locations add scope, and we quote that as a fixed price before work starts.
Your food is not a template. Your website shouldn't be either.
Tell us what makes your place different. We'll quote a fixed price and build the site around it.