Project index
Verified liveHospitality PlatformProduction

Dilpasand 

A cinematic public experience connected to reservation, content, customer, media, support, and payment services.

Open live product Open full system flow
Architecture knowledge graph15 connected nodes
System coreDilpasandHospitality Platform
01 / AttractStory, food, and atmosphere establish intent
02 / ChooseDifferent visit types get different conversion paths
03 / CoordinateApplication routes separate customer and operator work
04 / PersistOperational records and media use the right stores
05 / OperateProtected administration keeps the public surface current
06 / DeployClient, API, and proxy retain independent runtime boundaries
Next.js
React
Express
MySQL
AWS S3
Stripe
Docker
nginx
Architecture stage Technology dependencyMove pointer to inspect depth

System brief

A hospitality platform built around experience and conversion

Engineering focus
Full-stack product delivery
Domain
Hospitality Platform
Delivery window
Production
System state
Verified live
3conversion paths
2content management surfaces
1responsive hospitality system

The engineering move

Complex behavior, made operational.

Constraint

The product problem

A restaurant site must sell atmosphere without hiding practical intent. Menu, table booking, private dining, catering, location, and story all need distinct routes while content and reservations remain maintainable by operators.

System

The architecture decision

The Next.js client composes media-rich public routes with reservation forms, blog content, menus, maps, galleries, testimonials, newsletter, and analytics. Express services separate users, support, editorial content, payments, and persistence behind Docker and nginx boundaries.

Outcome

The operating result

Guests can understand the brand, inspect the menu, plan a visit, request a table or group event, and continue into a direct communication path without leaving the product experience.

Delivered capability

What the system actually does.

01

Menu, story, gallery, media, and location experiences

02

Table reservation and date-selection flows

03

Private dining, group booking, and catering paths

04

Blog publishing and protected administration

05

Newsletter and transactional email workflows

06

Customer accounts and support operations

07

S3 media and MySQL application state

08

Responsive delivery with Docker and nginx

Full system flow

The Mermaid diagram, rendered.

The interactive graph above is the executive view. This is the detailed service, data, control, and delivery path reviewed from source.
Mermaid / system architecture120%

Rendering the reviewed system flow

Drag the horizontal viewport at higher zoom levelsView .mmd source

Production architecture

A concrete path through the system.

Each stage below comes from the reviewed source tree, routes, services, infrastructure, and deployment evidence.
  1. 01
    Attract

    Story, food, and atmosphere establish intent

    Video, editorial sections, menu exploration, galleries, social media, testimonials, and location content build the public experience.

    Next.jsMediaAnalytics
  2. 02
    Choose

    Different visit types get different conversion paths

    Standard tables, private dining, group bookings, and catering preserve the fields and expectations of each request.

    React formsDate controlsValidation
  3. 03
    Coordinate

    Application routes separate customer and operator work

    Express controllers own users, support, editorial content, payment events, and reservation-adjacent workflows.

    ExpressAuthenticationEmail
  4. 04
    Persist

    Operational records and media use the right stores

    MySQL handles structured product state while AWS S3 stores uploaded visual and editorial assets.

    MySQLAWS S3Multer
  5. 05
    Operate

    Protected administration keeps the public surface current

    Admin and blog tools let operators manage content and reservation data without code changes.

    Admin UIBlog APIProtected routes
  6. 06
    Deploy

    Client, API, and proxy retain independent runtime boundaries

    Containerized services and nginx support repeatable deployment and clear network ownership.

    DockernginxVercel

Engineering judgment

The decisions behind the delivery.

Atmosphere has a job

Media and motion support menu discovery and booking intent instead of acting as isolated decoration.

Conversion paths stay domain-specific

A group event is not forced through the same flow as a two-person reservation.

Operators own freshness

Editorial and administrative surfaces reduce the cost of keeping menus, stories, and customer-facing information current.

Technical constellation

01Next.js02React03Express04MySQL05AWS S306Stripe07Docker08nginx
Dilpasand live restaurant homepage
Deployment evidence

This is running software.

Live product and source reviewed on 2026-07-16. The public link is provided as evidence, while protected product areas correctly remain behind authentication.

Open Dilpasand

Continue through the project archive

Next caseAI Platform Product Site