Cuinat

The challenge

Cuinat is a family-run homemade takeaway business with two locations in Palma de Mallorca. The menu rotates daily — over thirty dishes a day across rices, paellas, fish, meat, salads and Mallorcan specials — and the typical customer has fifteen minutes to eat well and pay honestly. That already works at the counter.

The challenge was bringing that same "see, choose, pay, take" flow online without turning it into a three-step bureaucratic process. And doing it in a business where day-to-day operations live in the kitchen, not in an admin panel.

What we built

• Bilingual brand site (ES/EN): half the traffic is local, half is tourists in Palma. Same content, two clean URLs.
• Visual daily catalogue: the menu changes, photos carry more weight than text. Gallery with a big photo, name and price — no long descriptive paragraphs.
• Online ordering integrated with FoodBooking: customers compose their meal, pay and pick a pickup or delivery time; the ticket lands in the kitchen without a human middleman.
• Corporate and event services: separate pages for private chef, corporate catering ("Angel 24" programme) and group menus — each with a clear CTA.
• Maps and per-location hours, with SEO for "takeaway food Palma" and Restaurant schema so Google Maps and local search pick it up on the first crawl.
• Newsletter and announcements integrated with the blog section for seasonal news (Sunday paellas, holiday menus, new menu items).
• Analytics and verification: Google Search Console, tracking tags and conversions on the order flow to see which dish goes to cart and which doesn’t.

Technical decisions that mattered

1. Duda instead of a custom CMS

The site runs on Duda. For a family business with two locations and a team focused on the kitchen, building a WordPress install or a custom site would have been over-engineering. Duda gives visual editing, hosting with CDN included (served by cdn-website.com), native multilingual support and forms without installing plugins. The decision wasn’t "use the most powerful tool"; it was "use the tool the client can maintain when we’re not around".

2. FoodBooking instead of a custom cart

The order flow — per-dish modifiers, per-location pickup hours, holidays, platform commission — is a product in its own right. Integrating FoodBooking solved the cart, the payment, the kitchen notifications and the iOS/Android apps without writing a line of backend. The rule here: clients pay for product value, not for pretty code; when an integration covers 95% of the need, that 95% gets bought.

3. Bilingual ES/EN from the start

Palma is a tourist destination. Having English from day one — not as a late-stage patch — doubles the SEO surface and captures both expat residents and tourists searching for "homemade food Palma". Content is maintained in parallel, not translated after the fact.

4. Photo before text

In takeaway, the dish sells. We bet on a big photo for each item — paellas, wraps, bowls, desserts — and short descriptions. It’s counterintuitive from a classic SEO angle (where "more text" usually wins), but in food, conversion goes up when the visitor sees what they’re going to eat in under three seconds.

Outcome

The site works as both an online shop and a brand calling card. The two locations show up in Google Maps with hours, photos and ratings tied to the site; online orders flow into the kitchen without manual intervention; and the menu is updated from Duda by someone on the team without touching code. The brand voice — #porquenosgustacocinar ("because we love to cook") — reaches the digital channel with the same intent it carries at the counter.

The most underrated decision in hindsight: choosing tools the client can run without us. If they switch development providers tomorrow, the site doesn’t fall over: it just changes hands.