Welcome! This page is for whoever is taking over and managing the wedding site (that's you, friend). It covers what the project is, where things live, how to run it, how to deploy it, and how to help the couple use the admin. It lives in the repo at mockup/help.html — just double-click it to open in a browser.
A one-wedding website for Nathan & Andrea. Two halves:
Design is "inspired by" a Canva template — the feel only. Don't reuse that creator's photos, names or copy. The full brief is in docs/spec/SPEC.md with screenshots in docs/spec/references/.
Non-goals: gift tracking, payments, seating charts, multiple weddings, guest accounts, livestreaming. Say no to these; it keeps the site cheap and simple.
| Piece | Mockup status |
|---|---|
Guest site (index.html) | Done as a visual mock: intro, hero, countdown (live), details, schedule, travel, FAQ, registry, gallery, footer. |
RSVP form (rsvp.html) | Form works visually, shows a thank-you. Nothing is saved. Honeypot field is in place. |
Admin (admin/index.html) | All 9 screens drawn with sample data. Only Look & feel actually works (colours/fonts saved in your browser and applied to the guest site). |
| Backend, DB, email, auth, Docker | Not started. See phases below. |
mockup/
index.html guest home page (all sections on one page)
rsvp.html RSVP form page
help.html this page
admin/index.html admin mockup (tabs)
assets/
style.css theme tokens (:root variables) + all guest styling
app.js intro, countdown, RSVP behaviour, applies saved theme
photo-*.svg placeholder "photos"
docs/spec/
SPEC.md the build spec — source of truth
references/ 8 design screenshots
README.md quick start
Theme system: all colours/fonts live in assets/theme.js (the preset list and the theme keys: bg, bgDark, text, card, cardText, accent, font, texture, intro) and are applied as CSS variables defined at the top of assets/style.css. The admin editor and the guest site both use that one file. In the real app, save this same JSON in settings.theme and call the same apply function. To add a preset, add one line to PRESETS.
Easy edits in the mockup: colours/fonts → top of assets/style.css. Placeholder names/date → search Nathan & Andrea and WEDDING in assets/app.js.
Easiest: double-click mockup/index.html. Fonts load from Google Fonts, so you need internet. Or serve it (needed if you later add fetch calls):
python serve.py # then open http://localhost:8080 (it also prints a network link to share on the same Wi-Fi)
Run it from the repo root. serve.py turns caching off so your edits show on refresh.
Tips: use the black bar at the top of every page to jump around. Replay intro clears the "already opened" memory. Add #skip to the URL to bypass the intro. Use your browser's phone-size view (F12 → device toolbar) — mobile is the priority.
From the spec. Stop and show Nathan after each phase.
| # | Phase | Done when |
|---|---|---|
| 1 | Skeleton + design: Next.js (App Router, TS), Dockerfile, theme tokens, intro, home, countdown, placeholder content; deployed to Coolify | Live URL shows the mockup look on a phone |
| 2 | Database (SQLite + Drizzle/Prisma), admin login, guest CRUD, CSV import, personal links /i/<code> | Add a guest, copy their link, it greets them by name |
| 3 | RSVP form, admin RSVP table, dashboard, CSV export | Guest RSVPs in under a minute and can edit later |
| 4 | Invitations: email templates (Resend/SMTP), sending, open tracking, reminders | Send a test, see "opened" |
| 5 | Admin editors: photos (sharp resize, B&W), theme, content, section toggles, live preview | Couple changes colours + photos with no code |
| 6 | Polish: OG images, accessibility, performance, backups, final README | Acceptance checks in the spec pass |
Keep it to one container: SQLite on a volume, photos on disk, no extra services. The mockup's CSS variables (--bg, --text, --card, --accent, fonts) are exactly the theme tokens the admin editor should write.
/data/db and /data/uploads. Without these, a redeploy wipes guests and photos./api/health), turn on auto-deploy for main.| Name | What |
|---|---|
ADMIN_EMAIL, ADMIN_PASSWORD | First admin account (created on first run). Change the password after logging in. |
SESSION_SECRET | Long random string for login sessions. Never commit it. |
RESEND_API_KEY | Email sending (or SMTP vars if swapped). |
EMAIL_FROM | Sender address — must be verified with the email provider. |
SITE_URL | Public URL, used in personal links and emails. |
Never put real secrets in git. Keep a .env.example with blanks and a .env (already git-ignored) locally.
/data/db and everything in /data/uploads.Share this section with Nathan & Andrea. Sign in at your-domain/admin with your email and password.
Guests → + Add household. A household is a person or family sharing one invitation. Set how many plus-ones they may bring and a group (family, friends…). Many at once? Import CSV (columns: household name, member names, email, phone, plus-ones, group).
{{link}} — that's each guest's personal link.Statuses: not sent → sent → delivered → opened → responded. Use Remind non-responders on the Dashboard (a single click).
Look & feel: pick one of nine ready-made themes (Olive Garden, Sage & Cream, Dusty Rose, Navy & Gold and more), then tweak any colour if you like — page colour, text, cards, buttons/accent — plus the font pairing, paper texture and the intro screen. The phone preview on the right is the real site and updates instantly. The Readability check warns you if text would be hard to read; Make page text readable fixes it in one click. Click Save theme to publish; Reset to default goes back to the original olive look.
Photos → Upload. Drag to reorder, add captions, mark one as the hero, tick B&W for the photo-booth look. Pick 3–4 for the intro strip in the strip builder. Portrait or square photos work best; they're resized automatically.
Content: names, date, venue, the handwritten note, schedule, FAQ, travel, registry links. Untick a section to hide it from guests.
RSVPs → Export CSV — one for the caterer (meals, dietary) and one for the printer (names, addresses).
Guests → find the household → Copy link (or QR) and resend it. They can change their answer from the same link until the deadline.
| I want to… | Do this |
|---|---|
| Change the date | Admin → Content (and Settings → timezone). Countdown follows automatically. |
| Extend the RSVP deadline | Admin → Settings → RSVP deadline. |
| Fix a guest's RSVP | Admin → RSVPs → Edit. |
| Add a second admin | Admin → Settings → + Add admin. |
| Go live with a password | Admin → Settings → Site password. |
| Update the app (developer) | Commit and push to main; Coolify redeploys. |
SITE_URL is right.EMAIL_FROM is verified, check spam, send a test to yourself./data/uploads volume isn't mounted. Fix the volume, restore from backup.