Haliviq
Back to WorkF&B

BBK Menu: Restaurant and Dish Discovery Platform, UX Design and Web Build

BBK Menu helps people decide where to eat in Bangkok and which dishes are worth ordering. With hundreds of restaurant and dish entries, the hard part is not the visual style but how the content is organized, searched and published. Haliviq led a UX/UI design phase first, testing the browsing, filtering and listing patterns against real restaurant and dish data, and only then built the website. We also set up a publishing workflow so the editorial team can add listings without waiting for a developer. This page covers the deliverables, process and technology.

Industry

F&B

Platform

Responsive Website

Year

2025

Services

4

Services Provided

UX/UI DesignWeb DevelopmentRestaurant Discovery SystemPhotography & Content Direction
BBK Menu

Project Objectives

  • Design an information architecture that stays easy to browse as it grows to hundreds of restaurant and dish listings.
  • Help readers go from a vague craving to a specific recommendation in a few steps.
  • Give the editorial team a content system for publishing new listings without developer involvement.
  • Organize categories, neighborhoods and cuisines so the content does not turn into a maze.
  • Build a technical foundation suited to long-tail restaurant and dish searches.
  • Use photography and content direction to make each listing page useful, not just filled in.

What We Delivered

  • A UX/UI design system for a restaurant-discovery content platform
  • A responsive website with filterable restaurant and dish listings
  • A restaurant discovery and recommendation browsing system
  • An editorial content structure for ongoing publishing
  • Photography and content direction for listing pages
  • Category, neighborhood and cuisine structures for navigation and search
  • A publishing workflow handover for the editorial team

How We Built It

1

UX/UI design phase

We designed the browsing, filtering and listing patterns before writing code, and checked the structure against real restaurant and dish data. Problems with the layout showed up on paper instead of in production.

2

Information architecture

We organized categories, neighborhoods and cuisines so the content can grow without turning into a maze. A reader can come in through any of them and reach the same listing.

3

Development

We built a fast, responsive website on top of the approved design system. Search and filtering run on a structure planned alongside the content model.

4

Editorial handover

We delivered a publishing workflow that the editorial team runs on its own. Adding a listing, with photos and categories, does not need a developer.

Technology & Tools

UX/UI design system, shared across listing, category and search pagesNext.js front end, for fast pages and clean URLsHeadless CMS for listings, where editors publish restaurant and dish entriesSearch and filter architecture, planned together with the content modelCloud hosting and CDN for quick image deliveryOn-page SEO foundation for long-tail queries

Results

  • The new website launched with a content system built to grow past its first listings.
  • Browsing and filtering follow the way people actually look for a place to eat.
  • The editorial team publishes without waiting on developer time.
  • The SEO structure targets long-tail 'best X in Bangkok' searches.
  • Categories, neighborhoods and cuisines keep a growing catalog easy to navigate.

FAQ

Short answers about this project.

The UX/UI design phase and the website build for a discovery platform like this typically take a few months together. The size of the first batch of listings affects the timeline.

A Next.js front end with a headless CMS for restaurant and dish listings, built on a search-and-filter architecture and deployed on a CDN-backed host.

For a discovery site, the structure is the product. Testing patterns against real data first avoids rebuilding the navigation once hundreds of listings are in.

Listings are organized by category, neighborhood and cuisine and can be filtered. The same structure serves both readers browsing and search engines indexing.

Yes. The headless CMS and publishing workflow let the editorial team add and edit listings on their own.

Yes. The listing, filtering and editorial publishing architecture applies to other local discovery platforms beyond restaurants. We adapt the categories and the listing format to the subject.

Read the Full Case Study

Have a project in mind?

Let's build your next project

Talk to Us