TEMPLATE GUIDE / SABLETIDE
A practical setup guide for the next property owner or agency.
01 / START HERE
Sabletide is a fictional property, and the rooms, setting, and services shown in this project are illustrative. Before using the site for a real property, replace its name, location, photography, room facts, service details, and visitor information with verified material. Remove any offer that is not part of your actual guest experience.
The experience entries are editable examples, not a promise that a particular activity is available. Confirm current dates, conditions, access information, materials, menus, prices, and booking arrangements with the people delivering each service. Keep the public descriptions specific to what you can offer, and update them whenever those details change.
02 / CONTENT
Stays holds each room’s introduction, cover image, gallery list, size, guest count, beds, amenities, access note, inclusions, arrival details, and booking link. Experiences holds the programme and practical details. Journal holds destination and stay stories.
Update collection items first; the index cards and detail pages use the same fields. Keep image aspect ratios consistent within lists for a calm rhythm.
03 / BOOKING
The Plan Your Stay inquiry component starts in preview mode. To receive requests, select it and enter your own HTTPS endpoint that accepts POST JSON; test delivery, validation, error handling, and a real reply workflow before publishing. You can instead direct room Booking Link fields to an external booking engine.
Each request contains name, email, arrival, departure, guest count, preferred stay, and an optional note. It does not hold inventory, take payment, or confirm a reservation. Update room capacities, dates, policies, and privacy information to match the real property; a guest should receive confirmation only through your connected service.
MOTION
Keep the movement, change the view.
CoastalAperture turns two photographs into a sea-glass journey. Water aperture is the opening optical lens; Joining shores combines two image sheets through a refractive tide. Both respond to native scrolling on desktop and phone, with damped waves from pointer or touch. Edit Photograph, Inner view, Opening and Motion in the component controls. Keep the Joining shores instance and its container on Auto height so its sticky sequence has room. The Pause motion control stops ambient water; user-driven scrolling remains available. Reduced motion and unavailable WebGL use a static photograph. CoastalDay provides three editable photo chapters. SiteChoreography adds optical glass layers to native images without changing CMS content. Remove an override to restore a native element.
Replace the illustrative photographs, then preview slow and fast scrolling in both directions on desktop and phone. Check the chapter buttons and pause controls. With reduced motion enabled, the complete content remains visible without the scrubbed or ambient sequence. Use shorter chapter headings when possible, and check wrapping after editing.
04 / LAUNCH
Replace this guide and privacy copy with your own. Add verified policies, response expectations, check-in and cancellation terms, analytics consent where needed, and a contact route that reaches your property.
Check every CMS item and page at desktop, tablet, and phone widths, verify focus and menu operation, and test the reduced-motion setting before publication.
SUPPORT
A little help, if you need it.
For template setup questions, write to the Lu Flow support address below. For a real stay, replace this section with the property’s guest contact information.