PROJECT / EDELWEISS
Edelweiss
Edelweiss shows Varun working in a different register: hospitality, visual warmth, product photography, and conversion details.
A cafe/restaurant web system with product imagery, reservation UX, SEO, team pages, and seasonal visual assets.
ACTUAL PROMPT / THREAD TRACE
push the app to github
WHY IT MATTERS
It proves the workflow is not only app logic. It is also taste, SEO, real business surfaces, and mobile reservation polish.
HOW TO READ THIS
Each entry is a dated design decision: the pain point, the response, the proof source, and the visual artifact when the archive had one.



DATED JOURNEY
DATE INDEXThe site started with place and appetite
Some products need logic. Hospitality needs feeling first.
Edelweiss carries cafe interiors, coffee imagery, team pictures, and seasonal drink assets.
That visual material changes the design problem: the interface should support warmth, not flatten it.
edelweiss-js public image library.

The cafe became searchable
A beautiful site is still invisible if search cannot understand it.
SEO guide and components in the repo show a serious layer for discoverability.
This connects to the current blog SEO work: metadata is part of the product surface.
SEO_GUIDE.md and SEO components in edelweiss-js.
The reservation form got tightened
Mobile booking is won in the last few pixels.
Reservation overlay reports show iterative fixes for narrow and tight mobile states.
This is a recurring Varun detail: he notices when the visible product almost works and keeps pushing until it actually fits.
reservation overlay report screenshots.

The product library became seasonal
Coffee, matcha, gluhwein, hot aperol: the site learned the menu's rhythm.
Seasonal product assets gave the site a changing visual vocabulary.
This is where design becomes business memory: what the cafe sells, when, and how it wants to feel.
Product image assets in edelweiss-js/public/images.
The repo got pushed as a product asset
Shipping is also preservation.
The Edelweiss thread confirms the repo was pushed to GitHub, turning local work into a durable project.
That matters for this blog because the workflow is not just making; it is keeping a trace.
Edelweiss thread: push app to GitHub.