Invitein is my own business: digital wedding invitations for Indonesian couples. Instead of a printed card, each guest gets a personal link on WhatsApp with the wedding details, an RSVP form, and a theme that fits the couple's culture.
It has just launched and has its first customer. The launch price is Rp 39,000 per invitation, and regular prices start at Rp 159,000.
A printed invitation is slow and expensive for a wedding with hundreds of guests, and the couple still tracks who is coming by hand. A digital one has its own requirements:
It is opened from WhatsApp, often on a slow connection, so it has to load fast without an app.
Every guest should see their own name on the cover, and the couple needs a ready message for each one.
Indonesian weddings differ by culture and faith: a Javanese, Batak, Minang, Balinese, Chinese Indonesian, church, or military wedding each needs its own look, greeting, and verses.
RSVPs and wishes have to land somewhere the couple can read without logging in to anything new.
One couple’s invitation must never break when I change a theme for the next.
How It’s Built
Invitein is a static site with no framework and no build step: one shared engine, a thin file per theme, and scripts for everything I repeat for each couple.
01
Theme demoThe couple picks one of 15 themes
02
Client copyOne script copies the theme and engine into its own folder
03
Wedding configNames, events, photos, music, and gift details in one object
04
Guest linksA guest list becomes a personal link and message each
05
WhatsAppThe couple sends each message from their phone
06
The guest opens it
RSVP and wishesSaved as a row in the couple's Google Sheet
Maps and calendarOne tap to directions or a calendar entry
Invitations: HTML, CSS, and plain JavaScript, with GSAP and Lenis for the premium themes.
RSVP: Google Apps Script writing to the couple’s own Google Sheet.
Illustrations: the Codex CLI and small Node.js scripts.
Hosting: Cloudflare Pages. The landing page and demos deploy through GitHub Actions; each couple’s invitation is its own Pages project.
One Engine, 15 Themes
The engine renders every section from one configuration object: the cover with the guest’s name, the couple, events with Google Maps links, a countdown with a Google Calendar button, a gallery, a love story, live stream links, a digital gift envelope with copy buttons, background music, and the RSVP form.
Each theme file sets only its palette, fonts, ornaments, and opening animation, such as carved wooden doors for Keraton, a gunungan that splits for Jawa, an angpao for Tionghoa, and a Pedang Pora arch for military couples. Premium and playful themes load an extra motion layer before the engine. Greetings and verses switch between Islam, Protestant and Catholic Christianity, Hinduism, Buddhism, and a general version, and the interface between Indonesian and English.
A Frozen Copy per Couple
A setup script copies only the chosen theme and the engine files it needs into a folder for that couple. Paths are root-absolute, so the same files work under /demo/ and at the couple’s own address. I fill in the configuration and photos and upload the folder as its own Cloudflare Pages project. A new invitation takes one to two days from the couple’s details to a link they can send.
Every couple keeps their own copy of the engine, so a change I make for the next couple can’t break an invitation that has already gone out. The couples’ data stays out of git.
Personal Links and RSVP
Every invitation ships with a guest link page. The couple pastes their guest list and gets a link per guest, with the name in the URL, and an invitation message in Indonesian or English ready to send on WhatsApp.
The RSVP and wishes form posts to a small Google Apps Script that appends a row to the couple’s sheet. The script takes a lock so simultaneous replies don’t collide, trims every field to a length limit, caps the number of guests, and escapes values that start like a formula, so a wish can’t run as a spreadsheet formula.
Illustrations Instead of Photos
The public demos use flat cartoon illustrations of one couple per theme instead of photos of real people. A small pipeline reads every image slot from the demo pages, generates an illustration for each one with the Codex CLI from a brief per theme, and swaps it into the template after I review it. Another script takes the screenshots for theme thumbnails and share images.
I built the engine, themes, and scripts with Claude Code and Codex, working from screenshots and a written set of rules in the repository, as I describe in Working with Opus 5.5.
Limitations
Frozen copies don’t get fixes. The same isolation that protects sent invitations means a bug fixed in the engine has to be copied into each live invitation by hand.
Two themes still mix old and new art. Kapel and Mutiara are moving to a Christian couple, and some of their images still show the earlier one.
Pretty URLs need Cloudflare./demo/bali and the old template redirects work only on Cloudflare Pages, so locally I open the .html files.
Lessons
Keep the theme file small
A theme only sets its palette, fonts, ornaments, and opening. Everything else lives in the engine, so a new feature reaches all 15 themes at once.
Freeze what you have delivered
A broken invitation can’t wait for the next release. A frozen copy per couple means some fixes by hand, which is worth it when a wedding happens once.
Use the tools couples already have
Guests open the link in WhatsApp, and couples read their replies in Google Sheets, so nobody installs an app or learns a dashboard.