INSTRUCTIONS

The file map (deployed into src/)

Don’t read the shipped files — this table and the contracts below are everything you need. Open a shipped file’s source only on a real fallback (runtime error / uncovered field), or to read a reference component’s pattern.

Astro stack additionally gets:

What you build — the design job

1. The event card + events index — your tile (image, date eyebrow, title, venue/online, price-from, sold-out badge) and rhythm, with the category filter (only when

   1 category), skeletons while loading, and an honest empty state — on useEvents.

2. The event page’s registration surface — branch on event.registrationType: TICKETING → your tier picker (name, description, price, quantity stepper capped by limitPerCheckout, non-SALE_STARTED tiers unbuyable) and the checkout CTA; RSVP → the built-in first/last/email form (a “can’t make it” option only when rsvpResponseType === "YES_AND_NO") and the confirmed/waitlist states; EXTERNAL → link out; closed → an honest closed state — on useEventRegistration, which owns ALL registration logic; you own how it looks.
3. The home page — hero, featured/next events (fetch in frontmatter → your components), brand story.

Plus the theme (@theme block, one edit) and the chrome (SiteLayout, one pass). Style everything with Tailwind utilities on the tokens.

The contracts your components consume

Wiring — Astro (default)

1. Set the @theme tokens (one edit); brand SiteLayout.astro (one pass — merge into the existing layout instead if another vertical is deployed).
2. Write your components under src/components/events/ (new names — don’t overwrite the references), swap the island imports in pages/events.astro and pages/events/[slug].astro. Listing island: client:load with the SSR props; registration island: client:only="react". Keep pages/event-confirmation.astro‘s route. Author your surfaces in as few messages as possible — batch multiple Writes per message.
3. Write pages/index.astro (home) — it exists from the scaffold; Read it before overwriting.

Wiring — React SPA (Vite etc.)

Import ./styles/global.css once at the app entry (needs @tailwindcss/vite in the vite plugins — deploy added the dep). Routes: /events → your listing; /events/:slug → fetch with fetchEventBySlug(slug) client-side, then your registration surface; /event-confirmation → the confirmation view (the checkout callbacks point at that path).

Hard rules

• Registration logic only through the shipped exports — useEventRegistration / startTicketCheckout / submitRsvp own the sequence (visitor-public tier read, reserve, createRedirectSession({ eventsCheckout }), rsvpV2). Never re-derive any of it, never hand-build a checkout/ticket-form URL, never route it through an API route or elevate — the whole flow runs client-side as the visitor.
• Branch on registrationType — never render an RSVP event with a ticket picker or a ticketed event with an RSVP form; respect registrationOpen.
• The RSVP form is built-in — exactly first name, last name, email; never fetch a form schema or add fields.
• Gate CTAs on canCheckout / canRsvp and surface error — checkout()/rsvp() can reject (sold out, sale ended, duplicate email, payment method not configured); the message is for the visitor.
• Confirmed states reflect REAL success: RSVP → render only from confirmed (and say “waitlisted”, not “confirmed”, for status WAITLIST). Tickets → the only success surface is /event-confirmation with Wix’s ?orderNumber= params; a visitor merely returning to the event page is NOT a success signal.
• Theme via the @theme tokens; no parallel theme files, no hardcoded palettes.
• Live data or an honest empty state — never mock events, tiers, or “X spots left”.
• Keep the detail page’s SEO pieces exactly as shipped.

Point the user to their dashboard

Give the owner the dashboard link plus the Events page — the deploy step’s JSON printed dashboardUrl; append /events for event management. Selling paid tickets needs a premium plan + a connected payment method (free/RSVP events work without) — mention it.

Seeding

Per seed/SEED.md — plain-data plan.json into seed-events.mjs from the project root. Seed events that exercise the UI (a ticketed event with 2 tiers, another ticketed one, a free RSVP event; future dates; an image per event).

Verify (before declaring done)

• Not done: /events renders live events SSR (view-source shows titles) through YOUR components; empty catalog shows your honest empty state.
• Not done: An event page branches correctly: ticketed shows your tier picker (prices, steppers, CTA disabled at zero tickets); RSVP shows the three-field form.
• Not done: An RSVP submits end-to-end: rsvp() resolves, your confirmed state renders.
• Not done: A ticketed checkout reserves and redirects to the Wix-hosted checkout (or surfaces the “connect a payment method” message when the site has none — that’s correct behavior).
• Not done: /event-confirmation renders (the honest no-order state on a direct visit).
• Not done: Event page view-source carries the SEO tags (Astro).
• Not done: Card/index/registration surfaces/home are YOUR designs on the tokens; data-layer/hook files unedited.
• Not done: Dashboard links handed to the owner (+ the paid-tickets premium note when relevant).