Week 1
Foundation
Next.js and Laravel set up, a database for categories, dishes and bookings, and the admin login. Menu fields were bilingual from day one.
Aroma Garden — A restaurant menu and booking system in Gothenburg
Website · Restaurant · Gothenburg
We built a restaurant menu and booking system for Aroma Garden, an Indian restaurant in Gothenburg. Guests see the full menu in Swedish and English and book a table online. Meanwhile, the staff change the lunch menu themselves in an admin panel.
The problem
A menu that changes daily, and a phone that never stops.
The lunch menu changes every weekday, guests speak two languages, and bookings came by phone in the middle of service. So the menu online was always a week behind, and a missed call meant a lost table.
The menu changes daily
A fresh lunch every weekday, with its own price, kept the website out of date.
Bookings by phone
Phone-only reservations landed during the busiest hours, so staff missed tables and lost notes.
Two languages, twice the work
Locals and visitors both need the full menu. Writing every dish twice by hand does not last.
Bookings in two places
Some guests book through TheFork, others call. The restaurant needed its own booking flow next to TheFork, not instead of it.
What we built
A restaurant menu and booking system the staff run themselves.
We built a restaurant menu and booking system on our own platform, with Next.js in front and Laravel behind. The staff edit dishes, prices and the weekday lunch in an admin panel. They write each dish once, and the site shows it in both languages. Guests book online and manage the booking with a number.
A menu the staff edit
The staff update dishes, prices, photos and the weekday lunch in the admin panel, with chili ratings and special dishes.
Online table booking with a number
Guests choose lunch or dinner, get a confirmation email, and manage or cancel the table with their booking number.
Write once, get two languages
Menu fields have been bilingual since day one, and the system translates categories automatically.
TheFork and direct booking
Direct bookings and TheFork live side by side, and the restaurant confirms and notifies guests by email.
How it came together
Four weeks to launch, then it kept growing.
The site launched with menus, online booking and the admin panel. After that came drinks menus, booking numbers, TheFork and the gallery, one release at a time.
Week 2
Public site and lunch logic
Home, menu, about and contact pages. Every booking picks lunch or dinner and sends a confirmation email, and the lunch menu changes by weekday.
Week 3
Menu details
Sub-categories, choose-from options and extra info on dishes, a separate drinks page, and automatic translation of categories.
Week 4
Design and search
A design pass on the hero, header and language switcher, and Google reviews on the home page. Then a sitemap and robots.txt that keep admin pages out of search results.
The result
From the lunch board to a booked table.
aromagardengbg.se went live after four weeks, with menus, online booking and the admin panel. Later we added drinks menus, booking numbers, TheFork next to the restaurant's own booking, and a photo gallery. So the restaurant now owns its bookings instead of renting them.
RIRafiqul IslamOwner
Explore our work
More digital solutions built for real needs.
Contact
Tell us what you need
Clear scope and requirements before development begins.
A practical approach built around your business needs.
Websites, web applications, and mobile apps under one team.
Clear communication throughout the project.
Newsletter
Useful ideas. Once a month
Practical insights on websites, web applications, mobile apps, and the technology behind better businesses. No noise, no daily emails—just useful things worth reading.