Publish Anywhere
One line, pasted onto any website, and the gallery appears there — borrowed, never handed over.

A gallery you can only see on our site is a destination. A gallery you can drop onto your own wedding site is a feature people share — it's how Rheveal travels beyond the people who were at the party.
The goalLet a host show their finished gallery on their own website — a wedding site, a Squarespace page, wherever — instead of only on Rheveal. And lay the groundwork so other services could plug in later.
- Designed the whole "publish anywhere" idea: a host copies one line, pastes it onto their own site, and their gallery appears there — live and always current. Publish once; it shows up everywhere it's been placed.
- Kept privacy the same: Rheveal still holds the actual photos, so the gallery is borrowed, never handed over. Hide a photo and it disappears from the host's site too, within the hour. Nothing about a gallery is reachable before the host releases it — same as always.
- Designed the future "developer" version (so other apps could integrate for lots of hosts at once), including a neat trick for sites that save their own copy: a permanent-looking photo link that Rheveal quietly re-checks on every single view — so "take it down" still works even on someone else's cached page.
- Built the first slice: a stripped-down, fast gallery page made to live inside someone else's site (no Rheveal clutter around it), the behind-the-scenes reader that feeds it, and a "Share & embed" panel in the host tools with copy-and-paste snippets.
- How it was built: each piece was implemented by one AI worker and then checked by a separate AI reviewer, with fixes and a final review over everything — a little assembly line with quality gates.
Built and set aside on the workbench — a few setup steps (pointing the embed's web address, switching on two services) remain before it goes live.
The reviewer caught that the embed was rendering "naked" — no brand colors, no fonts — because it wasn't loading the style file. It looked perfectly fine in the code and would have looked wrong on a real page. Caught and fixed before it went anywhere.