Website/In progress/2026/Built for Nebo
Nebo — landing for a group of venues
One page that routes a guest to three distinct venues instead of blending them into a single menu.
- A guest picks the right venue immediately rather than parsing a shared catalogue
- Each venue keeps its own character and its own storefront
- Static, with no build step and no backend — the page will outlast anything
The problem
Three different places with different crowds live under one name. A shared site makes them compete for attention on the same page and dilutes each of them.
How it works
A fork in the road: three banners, each leading to its venue's own storefront. No build and no backend — markup and styles solve the whole task.
The hard part
The point here is not code but care with what already exists. The domain already serves a live delivery storefront for one of the venues, with a menu, a cart and real orders. You cannot casually cover that with a new front page: it is somebody's money and somebody's orders, and the rollout order matters more than the page itself.
Evidence
- The live delivery storefront on the domain is captured as an explicit constraint, not discovered after launch
- The page needs neither a build step nor dependencies
- Three entry scenarios are separated and no longer compete
Stack
HTMLCSS