Events and venue walkthrough
Open Events to review the selected venue's published content. Editorial material should load from configured WordPress REST endpoints. An event deep link currently routes to its section rather than reliably resolving an exact event record; that remains open.
The walkthrough can describe local venues and their setting. Content images must be correctly attributed to the intended venue and not imply that a demonstrative booking is real.
Events are published content until booking is integrated
An event page can explain an occasion, date, venue, image, description and a link to additional details. The source of editorial records may be WordPress, accessed through a replaceable REST content provider. Publishing an event article does not imply that tickets or capacity reservations are available. Customer confirmations require a separate transaction provider or HSLG service.
Expected browsing journey
Select a venue, open Events and browse the list. Open an individual record to see the correct date, content and eligibility. If an event belongs to another venue, the interface should clearly identify the destination before moving there. A link to one event should navigate to that exact event, not merely the generic events landing page. The existing source still has gaps in specific event deep-link resolution; those must be corrected and tested.
Booking or purchasing event access
Do not implement a generic 'Book event' button by reusing a fictional presenter callback in the native app. A real action needs availability or ticket capacity, provider terms, authenticated customer state where required and verifiable acceptance. Event payment may involve a different tax/refund model from table ordering. That policy must be approved before coupling the flows.
Content quality and rights
Review event timezone, locale, recurring-date changes and cancellation notices. Images must be correctly licensed and associated with the right venue. The content feed should handle an unpublished/deleted post gracefully without displaying a stale acceptance button. A bookmarked event URL should not become an open redirect to an uncontrolled domain.
Operational verification
Test five-venue filtering, event open/close, exact deep link, expired event, WordPress REST outage and missing image fallback. Separate frontend display evidence from real ticket/booking proof. Record a public content identifier and source version rather than relying on a screenshot alone.