Work · Asia Aker Brygge

Asia Aker Brygge

Asia Aker Brygge

A WordPress Multisite build for an Oslo Asian restaurant, with a custom ACF-driven dynamic menu builder.

Started
2024
Role
Build
Live
asiaakerbrygge.no
Status
Live
Asia Aker Brygge

Asia Aker Brygge is an Asian restaurant on the waterfront at Aker Brygge in Oslo. INFIGO built its site, and the interesting part is not the one you can see from the front page.

01 · The context

A restaurant site is a menu problem wearing a website costume.

Most of what a restaurant needs from a website is undemanding: photographs that look like the room, an address, a booking link. Then there is the menu, which is the page people actually open, and which changes constantly. Seasons turn, a supplier falls through, a dish gets retired. The usual answer is a PDF, and a PDF is a document that was accurate once.

The second problem was that this was never going to be one restaurant. The same owners run Frenchie, and building two separate sites would have meant maintaining the same thing twice, forever, and watching them drift apart.

02 · The build

A custom menu builder, and one installation behind both.

  1. The menu is a content model, not a file. We built a dynamic menu builder in ACF, so a menu is composed of sections and dishes, and a dish knows its own name, description, price, allergens and heat level, in two languages. The kitchen edits it in the admin and the page rebuilds itself. Nobody exports anything.
  2. WordPress Multisite across both restaurants. One installation serves asiaakerbrygge.no and frenchie.no. Separate domains, separate brands, separate menus, shared code.
  3. The rest of the offer gets real pages. Private dining, events, bar, take-away and booking each stand on their own, because that is how guests search for them.

03 · The long haul

Built to be edited, not redone.

The point of the menu builder is that it removes the developer from a weekly task. Two years on, the restaurant is still changing its own menus and the site has not needed us to do it. That is the quiet measure of whether a small build was done properly.

What we delivered

  • A custom ACF-driven menu builder with bilingual dishes, allergens and heat levels.
  • WordPress Multisite serving two restaurant brands from one codebase.
  • Dedicated pages for events, private dining, bar, take-away and booking.
01

A menu that is content, not a PDF

The menu is the page most restaurant sites get wrong, usually by linking a PDF that goes stale the week it is uploaded. Here it is structured content: courses grouped into sections a guest can jump between, each dish carrying its allergen codes, its heat markers, its price and a description in both Norwegian and English. The kitchen changes it directly, as often as the kitchen changes.

asiaakerbrygge.no/restaurantmeny
A menu that is content, not a PDF
02

Two restaurants, one installation

Asia Aker Brygge and Frenchie run from a single WordPress Multisite. Each keeps its own domain, its own identity and its own menus; both share one codebase and one admin, so a fix or an improvement lands on both at once. Adding a third restaurant is a new site in the network rather than a second build from nothing.

frenchie.no
Two restaurants, one installation
03

Everything else a restaurant actually sells

A dining room is only part of the business. The site also carries private dining and events, the bar menu, take-away, and booking, each with its own page rather than buried in a paragraph on the front page, because guests arrive looking for one specific thing and rarely the same one twice.

asiaakerbrygge.no/selskap
Everything else a restaurant actually sells

Next

Want a project that reads like this in year five?

Send the plan See more work