Hospitality10 / 12
Restaurant websites
Sites with menus, reservations and admin for independent restaurants
- Status
- Live
- Period
- 2025 →
- Role
- Design and development
- For
- Restaurant guests, and the owners and staff who manage the menu and bookings.
Problem
Independent restaurants need a site that shows the menu accurately and takes bookings, without paying for a platform that owns their customers.
A series of restaurant sites built in 2025 and 2026: Casa Julio in Palma de Mallorca, Don Or, and Strandrestaurant Badezeit on Sylt. Each combines a landing page with reservations and a back office.
Case study
Casa Julio has a landing page, a digital menu with allergen tags, real-time reservations and an admin area, built with Next.js 16 and Tailwind v4. Don Or combines a landing page with a reservation system. Badezeit on Sylt pairs a site with restaurant management, built with Next.js 15 and Prisma.
These projects are where the hospitality background shows most directly: allergens, table logic and staff-side tools come from how a real service works. A separate floor-plan editor, tableo, came out of the same line of work in 2025.
Architecture
Next.js applications styled with Tailwind, with reservations and menu data in a database (Prisma in the Sylt project) and an admin area per site.
Engineering decisions
- Allergen tags are part of the menu data, not an afterthought.
- Reservations update in real time so the floor sees the same state as the site.
- An admin area on every site, so staff can change the menu without a developer.
Challenges & trade-offs
Each restaurant works differently, so the common parts had to be separated from the venue-specific ones. That lesson fed directly into Enigma.
Verified results
- Casa Julio live at casajulio.vercel.app
- Don Or live at don-or-landing-1.vercel.app
- Public repositories on GitHub for casajulio and don-or-landing
Status labels are factual: nothing here is presented as more finished than it is.