Astro theme
Janapar
A one-page website theme for a tour operator, with a detail view for each tour and a request that names the tour, for designers, developers, and agencies building a tour operator's website.
$99 one-time · unlimited projects · future updates included
What you receive
- The complete Janapar source: a one-page website for a tour operator, which you configure from one TypeScript file.
- Buyer documentation: install, customize, assets and rights, deploy, and troubleshooting.
- One fictional demo configuration with fourteen placeholder pictures you replace with your own photographs. The pictures are AI-generated illustrations, and are not photographs of the places the demo names.
- 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 Janapar repository on GitHub, where every future release of Janapar 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 business's name, and the page's title and description.
- The words of every section, and of every button and link.
- The tours: for each, a photo, a title, a price as text, how long, how hard, how many, and a description.
- One tour shown large, with the plan of its day, or none.
- Four short facts under the hero, why to go with you, and what is included.
- The guide, a gallery with captions, figures and reviews or neither, and questions with answers.
- Where you meet, and the rows under it: start times, the season, the languages you guide in.
- Contact destination (email, WhatsApp, or a booking page), a phone number, a map pin, and the message a request carries.
- 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 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 Janapar 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 Janapar 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 Janapar, 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 Janapar 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 Janapar 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 Janapar license · Purchase terms
What this release does not do
- One business, one page, one language (English).
- No CMS: content lives in a TypeScript file. The tours are what that file says; changing them is an edit and a deploy.
- No booking system, calendar or payments. The page does not know which dates are free, holds nothing and sends nothing: a request button is a link to wherever the business takes requests, and the message naming the tour travels only in an email link or a WhatsApp link.
- What is included is one list, shown in every tour's detail view. There is no per-tour list.
- Opening and closing a tour's detail view is a step in the browser's history.
- No map: the drawing beside the meeting point shows no real place. Directions links are shown once you give a map pin.
- The example pictures are AI-generated illustrations, not photographs, and not pictures of the places the demo names: replace them before a live commercial launch (a licence condition, not advice). The demo says so on its page in two lines you remove with them. The build refuses a switched-on site that still carries the claims it lists; the customize guide has the list.