Hospitality Website / 2026
Harbor Ember Cafe
Premium hospitality proof-of-work site
Case study
The project at a glance
Overview
Harbor Ember Cafe is a synthetic premium restaurant/cafe concept used to prove a controlled website build, QA, and proof-capture workflow.
Problem
The goal was to build portfolio evidence without using unauthorized client assets, real claims, or external media.
Solution
Create a scoped Vite + React + Tailwind homepage using procedural visuals, then validate desktop and mobile browser behavior.
Outcome
The first vertical slice and Section 2 are implemented and locally validated as private proof-of-work material.
Tools used
Stack and proof
Public evidence boundary
Desktop and mobile browser QA passed for the first vertical slice, with proof records stored locally.
Role
Frontend, visual direction, responsive QA
Case study system
What this project proves
Harbor Ember Cafe is a controlled hospitality website proof-of-work project built to show premium visual direction, responsive implementation, and proof discipline without using client assets.
Framework
Vite
React, TypeScript, and Tailwind CSS homepage slice
Viewport QA
2
Desktop and mobile browser QA records exist locally
Assets
Clean
No copied screenshots, logos, or real client media
Status
Slice
Hero and signature-items section implemented
Process
Build path
- 01
Keep the concept fictional
The site is a synthetic hospitality concept, which makes it useful as proof-of-work without implying a real client relationship.
- 02
Build a premium first slice
The implemented scope focuses on a polished homepage shell, visual hero, and signature item section instead of a sprawling template.
- 03
Validate browser behavior
Local QA records cover desktop and mobile rendering, hierarchy, spacing, CTA clarity, and lack of blocking runtime issues.
- 04
Keep proof boundaries explicit
The local project documents what was and was not captured, including asset use, proof capture, and source changes.
Evidence
Source map
What can be shown publicly, what stays local, and what still needs proof before launch.
Public screenshot
Public-safeA public-safe homepage preview is already used by the carousel and case-study visual section.
Browser QA report
Local-onlyDesktop and mobile validation notes support the proof-of-work story.
Asset boundary
Public-safeThe project is fictional and avoids real restaurant assets, logos, prices, or client claims.
Next
What needs to happen before this is final
- Package the screenshot proof into a cleaner case-study visual sequence.
- Extend one more section only after a scoped brief is defined.
- Convert local QA notes into concise public portfolio proof copy.
Visual evidence
Public-safe presentation assets