Astro theme
Nauras
A one-page website theme for a tasting-menu restaurant, with a heat dial that rebuilds the menu and a table request for the visitor to send, for designers, developers, and agencies building a restaurant's website.
$99 one-time · unlimited projects · future updates included
What you receive
- The complete Nauras source: a one-page website for a tasting-menu restaurant, which you configure from one TypeScript file.
- Buyer documentation: install, customize, assets and rights, deploy, and troubleshooting.
- One fictional demo configuration with seventeen placeholder photographs you replace with your own. The photographs are AI-generated.
- Typefaces installed by npm as @fontsource packages under the SIL Open Font License; no font files are bundled in the repository.
- The Vlavera Professional License v2 in the repository.
- Read access to the private Nauras repository on GitHub, where every future release of Nauras is published.
Stack
- Framework
- Astro 7.3.5, static output, one page
- Language
- TypeScript 5.9.3
- Styling
- Plain CSS — no Tailwind, no UI library
- Fonts
- Self-hosted via @fontsource (SIL Open Font License)
- Tests
- Vitest 3.2.7
- Requirements
- Node.js 24.x, npm 11 or newer, Git, and a GitHub account
What you configure, and what needs code
Configuration only
- The restaurant's name, as a wordmark, and the page's title and description.
- The words of every section, and of every button and link.
- The dial: two to five heats, their names, and where it starts.
- The courses: for each, one or more forms served from a given heat upward, each with a name, a line, a description and a photo or none. A course can be held back below a heat, with another in its place.
- Opening hours by weekday, the time zone, and when last orders are said.
- What the page says while the restaurant is open, at last orders, while it is closed, and on a closed day.
- The table, the chef, the room, a long table, and reviews or none.
- The table request: where to sit, party sizes, how many nights are offered, its words, and the subject and first line of the message it sends.
- The address, and how to find the door.
- Contact destination (email, WhatsApp, or a booking page), a phone number, an email address, and a map pin.
- Photos.
- Indexing and canonical site URL. A production build stops without the URL; deploying through Vercel's Git integration sets it for you.
Needs a code change
- Page layout and section order.
- Colour palette, the colours of the heat ramp, and typography.
- A second language.
Support, updates and deployment
14 calendar days of email support from the order date, for installation and the Vercel Git-integration deployment documented in the package. There is no response-time promise, and customization work, other hosts, and general development consulting are outside it.
Your purchase includes access to the Nauras repository and every future release published to it, including major versions and redesigns. Vlavera publishes releases when it chooses; there is no schedule. If the repository is ever retired, you get 30 days' notice by email and keep every release already published.
Deployment is tested on Vercel through its Git integration, on a plan that permits commercial use. The Vercel CLI path and other hosting environments are untested in this release.
The full guides (install, customize, assets, deploy and troubleshooting) are in the Nauras repository, which you get access to when you buy. This page covers what you need to know before that.
License
- Unlimited projects.
- One license covers every website you build with Nauras, for yourself or for your clients. There is no project limit.
- You hand the finished project to its client, who may keep, host, maintain, and modify it indefinitely.
- Before you hand over the code, give your client this license and get their agreement to its restrictions. They get that one site: they can't build another project from it or pass it on as a theme.
- You may not sell, share or redistribute Nauras as a theme, template or starter, whether you've changed it or not.
- Keep the source in a private repository, never a public one. Putting the finished website online is fine; publishing its code is not.
- Don't add anyone to the Nauras repository or share your access to it. Your employees and contractors get the code from you privately, for example from your own private repository.
- Before a website goes live commercially, you must replace the demo imagery with media you have the rights to use. This is a condition of the license.
This is a summary. The full license is what applies. Read the Nauras license · Purchase terms
What this release does not do
- One restaurant, one page, one language (English).
- No CMS: content lives in a TypeScript file. The menu is what that file says; changing it is an edit and a deploy.
- No booking system. The table request does not know whether a table is free, holds nothing and sends nothing: its buttons are links to wherever the restaurant takes requests, and the request travels only in an email link or a WhatsApp link.
- The dial, a course's detail view and the table request need the page's script. Without it the page shows the menu at its default heat.
- Open and closed need opening hours that are the same every week.
- No map: the drawing beside the address shows no real place. A directions button is shown on phones once you give a map pin.
- The demo's dish names, and the words it uses for the nine moods of its menu, have not been checked against a source. They are content you replace.
- The example photographs are AI-generated, not photographed: replace them before a live commercial launch (a licence condition, not advice). Two of them show the demo's name painted in the room. The build refuses a switched-on site that still carries the claims it lists; the customize guide has the list.