Kindly
RSVP
Please respond by 1 December 2026
Let’s find your invitation
Enter the name on your invitation, or the code printed on it. One form covers everyone in your household.
Mockup: names you can try. The real version matches against a private guest list on the server — the list never reaches the browser.
Rina van Wyk— single guestde Vries— couple, travelling from the NetherlandsBritz— family invited with three childrenThomas Bakker— guest with a plus oneNortje— three households, so you get the disambiguation stepNT-1042— straight to a household by invitation codeSmith— no match, so you get the fallback
Which household is yours?
We found more than one match — please pick the right one.
We can’t find that name
We looked for “” and came up empty. It may be spelled differently on our list, or the invitation may be under someone else’s name.
Please WhatsApp or email us and we’ll sort it out straight away — don’t worry about it.
Real contact details needed TBC
Invitation
RSVPs have closed
We closed responses on 1 December 2026 so we could give the venue and caterer final numbers. If something has changed, please WhatsApp us directly — we’ll do our best.
Email usThis is a design mockup — nothing is submitted anywhere. On submit the
answers are written to sessionStorage and you’re taken to the confirmation page.
The header photograph and the envelope are the couple’s own, recovered from the current site.
Working in this mockup: household lookup with accent-insensitive matching, the disambiguation step, the no-match fallback, per-guest attendance and dietary capture, conditional questions that only appear when someone is attending, inline validation with a linked error summary, a draft saved to this device as you type, a honeypot, and double-submit protection.
Production adds: a serverless endpoint that re-validates server-side,
writes to the private guest sheet, and emails a confirmation with a calendar invite.
See output/planning/WEBSITE_PLAN.md §6.