81 lines
2.4 KiB
Markdown
81 lines
2.4 KiB
Markdown
# 03. Public Website and Search
|
|
|
|
## Purpose
|
|
|
|
Define the customer-facing browsing experience before any booking logic is built.
|
|
|
|
## Scope
|
|
|
|
- Homepage layout and sections.
|
|
- Property listing page.
|
|
- Property card content.
|
|
- Filters and search controls.
|
|
- Property detail page content.
|
|
- Contact page.
|
|
- Editable content pages.
|
|
|
|
## Proposed Public Experience
|
|
|
|
### Homepage
|
|
|
|
- Hero with primary booking/search CTA.
|
|
- Availability search panel.
|
|
- Featured properties.
|
|
- Business introduction content.
|
|
- Key selling points.
|
|
- Location highlights.
|
|
- Testimonials.
|
|
- Contact/enquiry CTA.
|
|
|
|
### Property Listing
|
|
|
|
- Show published properties only.
|
|
- Support cards with image, name, area, summary, sleeps, bedrooms, bathrooms, price from, key amenities, and availability state.
|
|
- Provide filters for dates, guests, bedrooms, pets, location, and amenities.
|
|
- Hidden or clearly marked unavailable properties when date filters are active.
|
|
|
|
### Property Detail
|
|
|
|
- SEO-friendly dedicated page per property.
|
|
- Gallery, summary, description, location text, capacity, amenities, rules, times, pricing summary, availability calendar, booking panel, testimonials, and optional FAQs/related properties.
|
|
- Actions for date selection, guest count, availability check, price preview, booking start, and enquiry.
|
|
|
|
### Contact and Content Pages
|
|
|
|
- Contact form with name, email, optional phone, and message.
|
|
- Editable content pages for About, Local Area, FAQs, Terms and Conditions, and Privacy Policy.
|
|
|
|
## What Needs to Be Done
|
|
|
|
- Define the public navigation and page hierarchy.
|
|
- Define the homepage sections and CTA placement.
|
|
- Define listing filters and result states.
|
|
- Define the property detail page sections and actions.
|
|
- Define the contact and content page requirements.
|
|
- Define the public messaging hierarchy so users can move from browse to booking without confusion.
|
|
|
|
## Page Flow
|
|
|
|
1. Homepage
|
|
2. Property listing
|
|
3. Property detail
|
|
4. Availability check
|
|
5. Booking start
|
|
6. Contact/enquiry if the user is not ready to book
|
|
|
|
## Acceptance Criteria
|
|
|
|
- A customer can understand how to browse, inspect, and contact the business from the plan alone.
|
|
- The listing and detail pages have clear required content.
|
|
- Filter requirements are explicit.
|
|
- The search flow is compatible with the later booking rules.
|
|
- The public journey is ordered and consistent across pages.
|
|
|
|
## Dependencies
|
|
|
|
- Content architecture and data model.
|
|
|
|
## Notes
|
|
|
|
- This step should not decide pricing or payment behavior yet.
|