Celebrations
A private site for each family celebration, from birthdays to baby showers and anniversaries, set up from an admin in a minute: photo sharing from every phone, a sealed time capsule, a live trivia game on the TV, and a keepsake download when it is over.
- Guests join from one link or QR code: no accounts, no app, no typing a code.
- A live trivia game for the whole room, scored on the server and shown on the TV.
- When it is over, the site becomes a read-only keepsake with a one-file download of everything.
- A new event, of any kind, is set up from the admin in a minute, with no code changes.
The brief
Every family celebration ends the same way: a group chat full of photos nobody can find a week later, and the best stories told once and forgotten. I wanted one private place for each event that guests use before, during and after, and that I can set up again for the next one, whether that is a birthday, a baby shower, an anniversary or a retirement. The first was a family 50th. The guests ranged from teenagers to grandparents, so it had to work on any phone with no app and no sign-up. It had to be private: family photos, not a public page. It had to carry the night itself, on the TV, without anyone babysitting a laptop. And it had to cost nothing to run.
What I built
A private site inside my existing Next.js app, plus a slideshow for the TV at the venue.
One link in. The invite link and the QR codes on the tables carry the party code, so guests tap and they are in. The first time someone shares, they give their name, and a signed cookie remembers them. Pages are never indexed, and photos are served privately so no cache keeps a copy.
Photos from every phone. Guests add as many photos as they like, old scans and new shots. Each one is decoded in the browser (iPhone and Samsung HEIC too), turned the right way up, and re-encoded at two sizes: a 2,560-pixel copy for the TV and a small one for grids. A 10 MB camera photo becomes well under 1 MB, and re-encoding removes EXIF data, including GPS location. Files go straight from the phone to storage through signed URLs; the server checks each one before it appears.
A time capsule. Guests write messages that nobody can read, not even the guest of honor, until the host opens the capsule. The TV then plays a reveal: who wrote, a countdown, confetti, and every message in turn.
A slideshow that runs all night. The TV shows every photo once per cycle in a fresh shuffle, never the same one twice in a row. New uploads jump the queue with a "Just shared" badge, and between photos come a "scan to add yours" card, moments from a timeline of the guest of honor's life, and videos. It keeps the screen awake, skips anything that fails to load, and restarts itself if it stalls.
A live game for the room. "How Well Do You Know…?" puts a QR code on the TV; everyone joins from their phone and answers against a 20-second clock. Answers are scored on the server, 500 for being right and up to 500 more for speed, then the TV shows how the room voted, the leaderboard, and a podium at the end. It runs itself, and the host can pause, skip, or end it from their phone. Guests send in the trivia questions beforehand; the host approves the good ones.
Games for any time. Guess the Year (slide to when a photo was taken), Who Said It? (family sayings), solo trivia, and a deck of photo challenges.
After the party
A party site usually dies the morning after. This one closes. One tap in the admin turns it into a keepsake: guests can still look through every photo, message, and game, but cannot add more.
Everyone can then download the whole party as one ZIP. It unzips to a single folder with every photo at full size, named by year and by who shared it, every message as plain text for printing, and a page that shows it all offline in any browser: messages, photos by decade, and the timeline, with no scripts, so it will still open in twenty years. The archive is streamed as it is built, so a party with thousands of photos downloads straight away and costs the server almost no memory. Sealed messages stay out of guests' copies until the capsule is opened.
How it works
Live without extra services. Updates reach phones and the TV through Postgres NOTIFY and
Server-Sent Events, the same system the client portal uses, with polling as a fallback. The live
game is driven by conditional updates, so when the TV and a dozen phones all ask to move it on at
once, exactly one does.
Built for the next one. A new celebration takes a minute in the admin: pick what it is (birthday, baby shower, anniversary, wedding, retirement, graduation, reunion), who it is for and when, and the site starts with fitting wording, timeline, photo challenges and captions, plus its own address and party code. A baby shower greets guests with "A baby shower for Maria and Sam", not "turns 50". Everything is editable from the browser, several events can run at once, and each one's photos and messages stay apart and stay up as a keepsake.
Nothing to pay for. It runs in the app and database I already host, and photos live in a Cloudflare R2 bucket on its free tier, with no fees for serving them.
Tested where it counts. Unit tests cover the slideshow order, game scoring and timing, the signed tokens, the content file, and the keepsake's ZIP writer, whose archives are read back and checked byte for byte, past the 65,535-file limit where ZIP64 takes over.