Hospitality website · 2026 · Live
Tuesday Lounge Bar
A venue website for Tuesday Lounge Bar, built so the menu, location, contacts, and table enquiry stay one tap away.
- Live in production
- Source on GitHub
- Mobile-first layout
- Russian and Kazakh
Overview
Most people open a venue website on a phone while deciding where to go. The site keeps the atmosphere of the bar, but puts the practical information where a phone user reaches first.
Context
A lounge bar website is read in a specific situation: on a phone, in the evening, by someone deciding where to spend the next few hours. That situation set the priorities more than any design reference did.
The problem
A dark hospitality design hides important text and actions very easily. The site had to feel like the venue without making visitors hunt for basic information.
The system, step by step
- Venue and atmosphere
- Menu
- Location and contacts
- Table enquiry
- On mobile the practical content moves up
Architecture
Content-driven pages, no backend required
- Next.js
- TypeScript
Order and spacing change for small screens
- Responsive CSS
Static production build
- Vercel
Key decisions
Question
Atmosphere or usability first?
Contrast instead of heavy effects to separate actions from mood.
The venue needed a dark, evening look. Adding glow and blur on top of that would have buried the one thing a visitor came for.
Question
What goes at the top on a phone?
Practical information moves up on mobile, not down.
Desktop can afford an atmospheric opening. On a phone the first screen is most of the visit, so it has to carry the menu and the location.
Question
Does this need a backend?
No database and no stored form data. Direct actions only.
The venue needed reading and contacting. A backend would have added deployment surface and maintenance the project had no use for.
What I built
A responsive venue site presenting the bar, with direct paths to the menu, the location, the contacts, and a table enquiry. Navigation labels say what they lead to instead of describing the mood.
What went wrong
The fixes were mostly about restraint: mobile spacing, heading length, readable contrast on dark surfaces, and keeping the key actions visible without filling the screen with buttons.
Outcome
Result
Visitors can understand the venue and reach the menu, location, contacts, or table enquiry without following a long sequence.
What I learned
On a business website the order of the content matters as much as the visual style. Mobile navigation made that especially clear.
Stack
- Next.js
- TypeScript
- Responsive CSS
- Vercel