A waterfront website for floating sauna and cold-plunge venues, built around the decisions a guest makes before arriving: whether to share the sauna or book the cabin, what the visit includes, how to prepare, and how to reach the water. The 13-page design pairs broad waterfront photography with expressive serif headings, practical visit guidance and a reservation-request journey.

Tidefire gives shared sessions and private groups their own space. Guests can compare prices and group sizes, read the house rules, understand the tidal gangway and facilities, and prepare a request with their chosen session. Harbor, Ember and Kelp color schemes each include Light, Dark and Auto appearance modes.

What is included

• 13 HTML pages: Home, Sessions, Shared Sauna, Private Sauna, Reserve, First Visit, Waterfront, Our Place, Questions, Contact, Privacy, Visit Terms and a custom 404 page.
• Shared-seat and whole-cabin request flows with dated sessions, party-size limits, price estimates, details, review, receipts, printing and reset.
• Unavailable-session feedback and interrupted-request recovery that retains the original request identifier.
• Preparation guidance, an illustrated arrival plan, access information, weather policies and native expandable questions.
• A local contact-notes tool for preparing and printing questions about access, groups or visit passes.
• 7 original AI-generated example images supplied in 3 responsive WebP sizes, plus local Instrument Serif and DM Sans fonts with their license notices.
• An editable SVG mark and favicon, responsive layouts, labeled form controls, keyboard navigation and reduced-motion support.
• Ready-made production files, editable HTML/CSS/JavaScript source, locked build tools, meaningful tests and an HTML buyer guide.

A request journey guests can follow

The form distinguishes individual places from a private cabin. A party cannot select a session with too few available seats, and changing the visit type or party size clears incompatible selections. Guests review their session and contact details before sending.

The preview includes an isolated demonstration with received, sold-out and interrupted responses. It sends nothing and never creates a real booking. In a connected production site, a receipt acknowledges delivery of the request; the host still confirms the booking and any payment separately.

Adapt the site to your waterfront

Edit business details, integer-cent prices, capacities, durations, time zone and dated sessions in the source data. Page fragments hold the venue story, preparation guidance, access details and policies. Images have independent file identities and alt text, while shared appearance values live in one palette source.

The download separates the publishable site, editable project and documentation. It uses semantic HTML, modern CSS and vanilla JavaScript without a frontend framework. The guide covers local viewing, builds, customization, hosting, form receiving and troubleshooting.

Requirements and scope

The ready-made site needs static HTTPS hosting. Local viewing and editing use Node.js 24.8 or later within version 24; rebuilding uses npm 11 and the included lockfile. Optional browser checks use an installed Google Chrome.

Actual requests require a buyer-provided receiving service. Live availability, storage, staff notifications, booking confirmation, payment processing and participation documents are not included. The guide explains server validation, duplicate handling and uncertain-request recovery. Hosting and connected services use the accounts and pricing chosen by the buyer; the local example needs no paid account or asset purchase.

The venue, people, prices and sessions are fictional. Included imagery is illustrative, and the finite example schedule expires. Buyers must supply accurate venue details and policies and maintain their inventory before operating the site. The preview-only Options control and simulated responses are excluded from the production site; their editable source is included.