Neighbourhood Café — Bilingual Brand Site & Menu
A full menu, a room you can feel, and one file to deploy.
Published anonymously at the client’s request
Overview
A single-page site for a café whose identity is bilingual from the wordmark down. It carries the full menu — around forty items across its sections — an about section, guest testimonials, and directions, in one self-contained HTML file with no framework and no build step.
What this proves
That a small hospitality brand can get a genuinely designed site without a CMS, a framework, or a monthly bill.
Key features
The whole menu, on the page
Around forty items are typeset directly in the page across its menu sections — not delegated to a PDF or a third-party embed. That means the menu is searchable, linkable, readable on a phone and indexable, which a PDF is not.
Scroll reveals that fire once
Sections animate in on an IntersectionObserver rather than a scroll listener, so the work happens off the main thread’s hot path and each element stops costing anything once it has appeared.
A bilingual wordmark, handled properly
The brand’s name exists in both Latin and Arabic script and both are used, set at sizes and weights chosen per script rather than forcing one typographic treatment across two very different letterforms.
Five sections, one continuous room
Home, about, menu, the experience, and contact — anchored so the navigation moves through one continuous page rather than loading four more.
The case for one file
A café site has a handful of jobs: say what the place feels like, show the menu, say where it is. A framework, a build pipeline and a deployment platform are all overhead against those three jobs, and every one of them is something that can break between the client and their site.
So this is one HTML document with its styles and behaviour inside it. It can be hosted anywhere, opened locally, emailed, and edited by anyone who can read markup. The tradeoff is stated plainly below: no CMS, so a menu change is a code change.
Not demonstrated by this project
Stated plainly, because a portfolio is more useful when it is precise about its limits.
- No content management — menu edits require editing the file
- No ordering, reservation or delivery integration
- The interface is English-only despite the bilingual brand mark
- No backend, database or forms that submit anywhere
- The testimonials are supplied content, not verified reviews
- No automated tests, CI or structured data
Portfolio assessment
- Visual design
- 7.0 / 10
- Technical complexity
- 3.0 / 10
- Interactivity
- 4.0 / 10
- Business value
- 6.0 / 10
- Portfolio appeal
- 5.0 / 10