Maya & Daniel

Build me an elegant multi-section wedding website as an Astro site (a real minimal Astro project — package.json, astro.config.mjs, src/pages/index.astro, small components, no SSR adapter — that builds to static files with astro build).

Before you build, ask me these questions in one message and wait for my answers. If I skip anything, choose a sensible default and tell me what you chose:

1. What are both your names, your wedding date, and the venue/city?
2. Where and when are the ceremony and reception, and is there a dress code?
3. Where should guests stay/fly into, and do you have a hotel block?
4. Which registry links should we include, and what meal options should the RSVP form offer?

Then build a complete, polished, responsive site with:

• A full-bleed hero with our names, the date, the venue, and a live countdown that ticks down to the exact ceremony date/time (and switches to a sweet “We’re married!” message once the date has passed).
• A sticky top nav that smooth-scrolls to each section, collapsing to a hamburger menu on mobile, with an always-visible RSVP button.
• Our Story — how we met, the proposal, told as a vertical timeline with a few dated milestones and a portrait photo.
• The Details — ceremony and reception times, the venue name and address with an “Open in Maps” link, and a dress-code note.
• Travel & Stay — nearest airports, the hotel room block (with a booking code and cutoff date), and directions/parking/shuttle info.
• Photo gallery — a tidy mosaic of 5–6 images with good alt text.
• Registry — a few linked registry cards (store registries plus a honeymoon fund), each with a short personal note.
• RSVP form — full name, email, accept/decline, guest count, meal preference, and a song request. It must validate (required fields, real email), reveal the meal/guest/song fields only when someone is attending, and show a warm success state that echoes their choices. No backend — handle it client-side.
• FAQ — an accordion answering plus-ones, kids, parking, weather, and the RSVP deadline.
• A footer with our names, the date, and our hashtag.

Design & content notes:

• Warm editorial wedding aesthetic: ivory/cream background, deep olive green, a terracotta accent, and thin gold rules. An elegant serif (e.g. Cormorant Garamond) for headings paired with a clean humanist sans (e.g. Mulish) for body. Generous whitespace, a quiet ornament divider, subtle hover motion.
• Use realistic content based on my answers — never “lorem ipsum”. Invent believable copy: a real story, plausible travel logistics, specific meal names, real FAQ answers.
• Use real images. Pull free photos that fit, e.g. from Picsum (https://picsum.photos/seed/our-wedding-1/1200/800, varying the seed per image) or real Unsplash direct URLs (https://images.unsplash.com/...) matching terms like engaged couple vineyard golden hour, outdoor wedding ceremony arch string lights, wedding table setting florals candles, couple holding hands walking countryside — with descriptive alt text.
• Keep dependencies minimal (just astro). Put all the wedding content in one src/data/wedding.ts file so a single edit updates the whole site. Persist nothing server-side; the RSVP success state is purely client-side.
• Keep it accessible (semantic HTML, labelled form fields, keyboard support, visible focus, good contrast) and mobile-first.

Add this exact line right before </body> so the site carries its badge:

<script src="https://spacefast.com/badge.js" data-example="invitation"></script>

When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:

1. Use ./dist as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has index.html at its root and no secrets, source files, .git, or .spacefast state.
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:

   PUBLISH_ROOT=./dist
   publish_files=()
   while IFS= read -r -d "" file; do
     relative=${file#"$PUBLISH_ROOT"/}
     publish_files+=(-F "files=@$file;filename=$relative")
   done < <(find "$PUBLISH_ROOT" -type f -print0)
   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"

3. From the { "data": ... } receipt, give me data.space.liveUrl, data.version.immutableUrl, data.claim.url, and data.claim.expiresAt. Remind me to claim within 6 hours. Keep data.claim.token secret.
4. Save data.space.id and data.claim.token locally (for example in an ignored, mode-600 .spacefast/state.json). For a quick update, rebuild the publish_files array above and publish to the same space:

   SPACEFAST_SPACE_ID=<saved-space-id>
   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
     "https://api.spacefast.com/v1/publish?wait=1"

   If an update after claiming returns space_claimed_credential_available, exchange the saved claim token once at POST https://api.spacefast.com/v1/anonymous-claim/exchange, save data.credential.accessToken, and retry with that access token.

Optional shortcuts and reference only: if the sf CLI is already installed, sf publish ./dist --wait does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: direct agent/API publishing · files and folders · claiming · updates and rollback