Friday, January 26, 2007

Our wedding website

If there's actually anyone out there reading this, you may be wondering why Nick is kicking my butt at posting lately. The answer is that we finally found a wedding location last weekend and set a date; so I've been busting my butt this week to finish our wedding website so that we can send out our invitations this weekend.

Each invitation comes with a login and password so that families can log in and RSVP online: it saves paper (whoever came up with the idea of 25 little vellum papers and envelopes folded inside other envelopes?), it saves stamps, and it saves time. They can also let us know what guests they plan to bring, and leave us comments (such as "Congratulations!" or "My son is going through an anti-yellow phase so he needs an entrée without anything yellow in it").

The brilliance of keeping all our RSVPs in a database is that—aside from having all the info in one place and not having to keep lists or hang on to a million little response cards—it makes it really easy to pull up some statistics about who's coming and who's RSVP'd. (I always feel stupid saying RSVP'd; I know we use it as a verb in English, but I can't help thinking répondez s'il vous plaît-ed every time I hear it.) I built an extra module for Nick and me to view some basic information about how many people have responded, and to see any comments people have left:

There will also—as soon as I make some phone calls about this—be info on local hotels, group reservations, maps to our house and to the reception location (a cute farmhouse in Bothell), and other useful information. In case you can't tell, I'm kinda proud of it all. Now I just need to send the actual invitations out so that people can start logging in and using the darned thing.

No comments: