Will I receive one HTML file or a framework project?

The default for a new project with no stack preference is one self-contained HTML file, built with Node.js 18+ after downloading its fonts once. Open the finished file offline; local hash routes connect its views. If you already have a framework or request one, the design is translated into real components and routes with local images/fonts. The documented default for an unspecified React framework is Next.js with TypeScript. React’s ReUI controls are an additional installation, not bundled runtime functionality.

Can I use the included photographs, and what costs extra?

The package includes 20 generated pictures and a slot-by-slot image plan. Neutral alpine scenes can remain disclosed placeholders only where they match the actual trip. Named locations, sample properties and all people require particular scrutiny; guide portraits do not identify your staff. Supply approved photos or authorize new pictures through your agent’s available image tool, whose usage can cost extra. The reference can be viewed without paying for new generation.

Does the booking flow reserve a place or take a deposit?

No. It demonstrates departure and room selection, guest controls, totals and a 20% example deposit, then validates inputs and shows a local acknowledgement. It neither sends the request nor charges or reserves anything. Connect real booking, email and payment services, replace the sample policies and test availability and pricing edge cases before treating it as a live service.

Alpine Travel Agency Landing

Previews from the publisher

Help travelers move from a mountain photograph to a specific trip: compare routes, meet the guide, inspect each day’s walk and prepare a booking request. Alpine Travel Agency Landing uses a restrained white headline over a valley scene, a dark glass search bar and staggered landscape photographs. Its Wander North example connects 30 routes and 20 pictures; your business needs its own verified trips, people, dates and prices.

What you get

A connected reference site rather than a single hero section: home, a filterable journeys index, eight journey details, experiences with three category pages, retreats, a guides index and three profiles, a journal with three articles, About, contact, FAQ, newsletter, booking, a three-question trip finder and a designed 404. These are the fictional example’s 30 routes, including the fallback; the final collection sizes can change with your brief.
A browse-to-request flow with live hero match counts carried into journey filtering, search, sorting, reset and empty results. Individual trips add a fact strip, highlights, an itinerary-based elevation diagram, daily distance/ascent accordions, inclusions, travel and sleep notes, months, a guide and related trips. Season/guide tabs, a swipe- and keyboard-operated trip rail and searchable FAQ provide other ways into the same content.
A booking prototype that carries departure, guest and room choices from a trip detail into a three-part form. It recalculates base price, single-room supplements, total and a sample 20% deposit, with guest controls and full-departure waitlist wording. The quiz scores pace, landscape and season to suggest a trip and alternatives. These calculations and recommendations use local sample data, not live inventory or an external recommendation service.
A photographic visual system: cool lichen backgrounds, pine accents, Geist with Geist Mono for small data labels, a 1296px content grid and rounded photographs. The full-height hero keeps one white display word, two short lines and four search selectors in a bottom-attached glass bar; a three-photo collage introduces the trips. The installation includes the template, style and route guides, image prompts, motion rules and quality checklist.
By default, an adapted self-contained HTML file with embedded pictures, fonts, styles and interactions, designed to open offline without visitor-time asset requests. Node.js 18+ and an initial font download are needed to build that file; its target is 5 MB with an 8 MB hard limit. An existing or requested framework project instead receives real routed components with local assets, rather than an embedded copy of the HTML.
Inline form feedback, visible loading and local confirmation states, plus keyboard navigation, a focus-managed mobile menu and reduced-motion behavior. No message is delivered, place reserved or money collected until real services are integrated. The supplied checks guide validation and browser inspection; their presence is not evidence that a new site has already passed either.

Before you choose

Organize the site around the traveler’s decision: where they can go, what each day demands, who leads it and what happens when they enquire. Keep scenic atmosphere separate from factual evidence. Review every data relationship after changing the collection sizes, and make the boundary between a convincing local demonstration and a connected travel business visible.

Good fit

A walking, cycling or ski operator needs visitors to compare departures and understand the practical details before making an enquiry.
A mountain lodge can map trips to rooms or packages, nights and local activities while retaining the photographic structure and useful detail pages.
A small travel brand needs a coherent family of trip, guide, story and company pages, with an offline file for review or a faithful implementation in its existing framework.

Not for

A ready-connected reservation, payment, email or live-availability system. The bundled interactions demonstrate the flow; production services and their rules are separate work.
A neon, predominantly dark or animation-heavy identity. The design depends on quiet photography, restrained pine/lichen colors and short, optional motion.
A site with no suitable imagery or verified travel information. Generated people and landscapes cannot establish a guide’s identity, qualifications, a route’s safety or a property’s facilities.

How to use

You say

/alpine-travel-agency-landing Build the Wander North site for our small-group walking trips in the Alps, with a page for every journey and guide.

Supply the company name, region, audience and kind of travel, then trips, guides and stories with dates, prices, descriptions and photographs. Include departures, group sizes, room supplements, inclusions and enquiry requirements where available. Missing details must be listed as placeholders for approval; do not fabricate qualifications, insurance, safety guarantees, reviews, awards or availability.
Choose the delivery within the existing project’s rules. With no project or stack request, adapt the standalone template and build it using the bundled asset inliner. For an existing or requested framework, create proper components and routes; the guide defaults an otherwise unspecified React framework request to Next.js with TypeScript. React controls use separately installed ReUI primitives; other stacks need their own accessible equivalents. Keep unrelated project files intact.
Map the page family to the actual business before filling it. A lodge may use rooms/packages, dining and spa; a tourism board may use places, hosts and enquiries. Keep trip, category, guide, article and departure relationships valid, including contextual links and return paths. Update query parameters, quiz scoring, comparison rows, seasonal defaults and fixed figure layouts as collections change; retain the three-image collage.
Plan photographs by subject, role, ratio, crop and destination page. Use supplied pictures or an available image-generation tool with permission; new generation may incur that tool’s charges, and no Skill-specific image API key is prescribed. The set should share subdued documentary light and believable regional detail. A picture may recur for the same trip or person across card/detail views, but must not represent unrelated entities.
Review all 20 bundled photographs before reuse. Eleven neutral alpine scenes may serve as disclosed placeholders for a matching mountain brand; the Dolomites, glacier, vineyard and two retreat-property pictures need subject-specific replacement. The three guide portraits and group scene are generated stand-ins, not photographs of your team. For a different region, replace the entire set, beginning with the hero. Check meaningful alternative text, responsive crops, headroom and WebP sizes.
Preserve the sparse hero and page rhythm while replacing the sample identity throughout: metadata, navigation, footer, contact details, stories, figures, quiz, departure dates, route IDs and booking extras. Use a one-word white hero heading, embedded Geist fonts, a 96px desktop search bar and the staggered collage. Keep per-page headings, landmarks, labels, focus rings, at-least-44px targets and motion that becomes immediate when reduced motion is requested.
Wire search choices into the journey list, verify filters and sort together, and check that trip selections reach the booking form unchanged. Test totals and supplements against your approved pricing rules rather than inheriting the demo’s deposit policy. Every listed journey needs compatible departures: the date helper assumes a nonempty set, and sold-out requests use a separate fallback guest limit. These are implementation details to verify when changing the data, not guarantees of production inventory handling.
Exercise contact, newsletter and booking forms with empty and invalid input, then inspect their loading and confirmation panels. Retain explicit simulation language until a backend exists. Test the quiz’s three steps, back/restart and alternatives; FAQ no-results behavior; tabs, carousel and mobile-menu Escape/focus return. Guard unavailable storage and clipboard features, and retain the submit-button handling needed in a scripts-only sandboxed preview.
Build the standalone file with Node.js 18+ and internet access for the one-time font download, then run the bundled design validator on the result. Strict mode checks embedded assets, sample leftovers, structural hooks, routes, forms and accessibility/motion markers, with an 8 MB size ceiling. The inliner can write a file before reporting missing assets, so an output file alone does not prove a successful build. For a hosted local-asset variant use the documented files mode; framework output needs its own type check and build.
Inspect every route and control in a browser at wide desktop, tablet and phone widths, including 1920, 1440, 1024, 768, 390 and 360px, and inspect the standalone file in the documented restricted iframe. Check photo subjects, typography, contrast, overflow, keyboard use, back/forward behavior and reduced motion. Screenshot, critique and fix through at least two review cycles. A static pass does not test these behaviors or visual quality.
Deliver the file or project path, explain which checks actually ran and list all unconfirmed facts, generated portraits and placeholder domains. Open the result, follow the complete search-to-request flow and request changes in ordinary language. Confirm the real booking, email, payment and privacy requirements separately before publishing a working business site.

Requirements and costs

You bring: Company name, region and the kind of trips you run · Your journeys, guides and stories with dates, prices and short descriptions · Your own photos, or permission for your agent to generate them
Dependencies: Node.js 18 or newer on your agent's machine, to run the bundled script that builds the single offline file · Internet access while the file is built, so the fonts can be downloaded once and embedded · An image generation tool in your agent for new photos, or photos you supply
Outside costs: New photos are generated with your agent's own image tool, which may incur that tool's usage charges. Supplying your own photos avoids this, and viewing the example costs nothing.
Publisher testing: v1.0.2 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT