Food delivery landing page
A landing page for a made-up Bangkok kitchen that delivers a home-cooked Thai lunch in a pinto, the stacked lunch carrier. Open the 3D pinto and its four tins stand apart. Tap one and it comes forward with a price tag that turns over to show what’s in it. It’s plain HTML, CSS, and JavaScript with three.js, and one list at the top of the script holds the dishes.
Baan Pinto is a landing page for a lunch delivery kitchen, shown here as a made-up Bangkok kitchen that brings a home-cooked Thai lunch to office desks in a pinto, the stacked enamel lunch carrier. The first screen is one pinto drawn live in 3D on a teak table in morning light, with a Thai headline and an Open the pinto button on its left. Open it and the carrier lifts away, the lid rises out of the picture, and the four tins spring apart into a row so the camera can look into each one. Every tin holds a photo of its dish and a label with its number and name. Tap a tin and it comes up to the camera while the rest of the table dims and a little steam rises, with a price tag beside it: the Thai and English names, one line about the dish, the price in baht, and chilli dots for the spice level. A switch turns the tag over to the ingredients and allergens. Below the hero come this week’s menu as four rows, how ordering works in three steps, the hours and delivery area, and one Order on LINE button. The four dish photos are computer generated.
This build is for a food business with a short menu that changes, like a lunch delivery kitchen, a weekly meal plan, a bento or tiffin service, or a café with a set of the day. It suits a kitchen that wants its page to feel like opening the meal itself, not reading a grid of cards.
Most food pages show the menu as a grid of cards or a PDF. Every dish looks the same, the set price gets lost, and nothing on the page feels like the food arriving.
You get the finished page with all three states working on a desktop and on a phone, plus a plain menu below it that works without 3D.
| Section | Purpose |
|---|---|
| The closed pinto | Put the real object on the first screen |
| Opening | Let the four tins stand apart |
| The tins | Show the food inside, all at one size |
| Focus | Bring one dish up to the camera |
| The price tag | Answer what people ask about lunch |
| This week’s menu | Keep a plain menu under the 3D |
| Ordering | End on one clear way to order |
The page should feel like a Thai home kitchen at eight in the morning: warm, calm, and a little nostalgic.
All three states work on a phone at 390 pixels wide, and nothing scrolls sideways.
The page works like lunch arriving. People open it, look inside, and the one way to order waits at the end.
A few things to know before you build on this one.
The page is one HTML file, one stylesheet, and one script, with three.js and the fonts copied in beside them, so there’s no build step and nothing loads from another site. The pinto is built in code from simple shapes: turned profiles for the tins and the lid, rings, cylinders, and boxes for the rims, lugs, and carrier, with the flower band, the lid petals, the teak grain, and the mat painted on canvases. Its reflections come from a small room of light cards baked once, and the only pictures are the four dish photos, 1024 pixels square. The dishes, prices, spice levels, ingredients, and allergens live in one list at the top of the script, and every tier is also a real button. Without WebGL, a drawn picture of the pinto stays in place and the menu below carries the page. The page code is about 90 KB, three.js about 720 KB, the fonts about 60 KB, and the photos about 1.1 MB.
Every state was run in Chrome at 1440 by 900 and at phone size, 390 by 844 with touch: the closed pinto, the open stack, tins in focus, the tag turned over, the way back, and the page below. Each state held 60 frames a second with no console errors, and the phone layout had no sideways scroll. A keyboard walk, reduced motion, and the page without WebGL were checked the same way. The runs were scripted in Chrome on a laptop set to phone size, so Safari, Firefox, a real iPhone, and a real finger scrolling over the 3D are still to be tested.
Captured from the live build: the closed pinto, the four tins standing apart, one tin in focus with its price tag, this week’s menu, and the phone view.





Custom build
You get a fixed quote before any work begins. Landing pages start at $1,490.
You pay the full price once the quote is agreed in writing.
The domain, code, content, and analytics live in accounts under your name.
Have a site already? Get the free audit
This build is for a food business with a short menu that changes, like a lunch delivery kitchen, a weekly meal plan, a bento or tiffin service, or a café with a set of the day. It suits a kitchen that wants its page to feel like opening the meal itself, not reading a grid of cards. The “Who this template is for” section above lists the three cases it fits best.
Yes. The full live build is embedded on this page, and the Preview button opens it in its own tab. There’s no signup, no watermark, and no time limit.
The exact production prompt that built Baan Pinto, with the art direction, the structure, and the engineering notes as they were written. You pay once in the prompt shop, and it stays yours.
Yes, that’s the plan for every template. I rebuild it around your brand, your copy, and your goals before anything ships. Start a project and tell me what you’re building.
Every section listed in the sidebar and in the overview table is built and working in the live preview. There are 7 of them, and the “Page sections” panel beside the article describes each one. Expand any row to read what it does.
No. Everything runs in a modern browser on desktop or mobile. Open the live preview and it works.
I rebuild every template around your brand, your copy, and your goals. Nothing ships as is. Tell me about your menu and I’ll adapt it.
Start a project Open the live template ❱