But first, the two of you must plan a wedding. What tools can help with the process? In this post, I focus on tools which can ease the wedding planning process.

We became engaged on New Years Day + 1, 2012, and picked a date just under four months. We also lived on opposite sides of the state. This made it important for us to have efficient tools to aid us in the process.

These tools cluster into two primary categories: Communication and Sharing. Many of these tools are high tech, many are 20th century tech, and a few are older.

Communication

• Phone
• Skype
• Gmail
• Fastmail.fm
• Facebook

Sharing

• Google Docs – collaborative documents
• Day One app – keep a journal
• Dropbox – file sharing
• Evernote – note sharing
• Remember the Milk – task sharing
• Google Voice
• WordPress – website software
• Amazon.com wedding registry
• Bed, Bath, & Beyond – wedding registry
• Magnetstreet.com – wedding invites

Phone & Skype

Call your fiance and call often! She wants to hear your voice, you want to hear your fiance’s voice, and you have a large number of things to discuss about the wedding, the honeymoon, and life ever after. Even if you live in the same town, you should be prepared to talk and text often.

When you’re apart due to distance or travel, seeing your fiance’s face via webcam can be a wonderful thing. Facial expressions and other non-verbal communication are greatly aided in this manner. This is particularly true when discussing important topics while getting to know each other better and while wedding planning.

Use Skype, Facetime, or a similar tool for communicating by webcam.

Email & Mail

Use your words to communicate. And occasionally, send each other gifts in the mail.

When you send your invites, you’ll be sending them through traditional mail. Learn the location of your nearest post office, and buy many stamps. For the invite design and printing, we used Magnetstreet.com. I used Pages to create the insert which contained additional information about locations, registries, and the wedding website.

I setup an RSVP email address through a domain configured with Fastmail.fm. If you need one-off email addresses, or simply don’t want to rely on a provider like Google Apps, I’d check out Fastmail (it’s owned by Opera).

I used Facebook to contact many friends to request a mailing addresses to send the wedding invite.

Document Sharing

Using Google Docs saved us an immense amount of time. For shared document collaboration, this was an easy decision.

We used it to keep track of the following:

• Invite List (Spreadsheet)
• Ceremony Schedule (Doc)
• Reception Schedule (Doc)
• Honeymoon Details (Doc)
• and other docs…

I make use of Evernote for additional notes. I’ve also journaled along the way using the Day One app for Mac in order to have memories and notes of this time.

File Sharing

We used Dropbox to share documents and photos. We also used it to share photos of us with our parents.

Task Sharing

We used Remember the Milk for sharing tasks with each other. Remember the Milk allows you to make and keep track of to-do lists, and you can share tasks with contacts as well.

It works well, but I would like to see improvements made. There is room for a startup to create a task sharing application in the vein of Paul Graham’s frighteningly ambitious idea to replace email.

RSVPs

For RSVPs, we used Google Voice. I setup a message which asked callers to give us their RSVP information. Anytime somebody RSVPed in this manner, I got an email and a copy of the message on my phone in the Google Voice app (for Android).

Twilio provides tools to make phone applications. If you want to get your code on to provide a richer wedding hotline experience, dig into the API and set something up.

Wedding Website

I went with a self-hosted WordPress installation, and bought the Dandelion theme at Themeforest.

Hosting via Linode (VPS), DNS via Zerigo, domains via Name.com.

Wedding Registries

We picked two registries: Amazon.com wedding registry, and Bed Bath & Beyond. I vastly prefer the experience of the Amazon registry because they have a better variety of products and the site is easier to search for products. However, it’s nice to have a store to visit to browse items. Having a registry with a physical retail store gives your wedding guests more options. Even in 2012, not everybody shops online.

Not everyone will buy gifts listed on your registry. People like to surprise you and your bride-to-be, or pick gifts with a personal touch. This can include kitchen items they’ve found invaluably helpful, pretty things they want to share, and antiques being passed down from previous generations.

You Have a lot To Do

You have many things to do as you prepare for your wedding. I hope this list of tools helps you in your preparations.

Disclaimer: I build websites and web applications for Amazon.com.

Seattle Saturday House is a weekly gathering of several people who meet and do … whatever they want! People work on projects, people talk about ideas, people conspire and hatch plans, and people play games with each other.

Last Saturday, people held a session about “hacks that make life simpler.” I took notes, and I’ve cleaned them up here for your viewing. If you’ve got any additional ideas to share or if you were one of the presenters and want to correct something I’ve posted here, please let me know by leaving a comment or emailing me (cal /at/ calvinfreitas dot com).

#1: Using Subversion to Manage Your Home Directory (/home/username/) — Patrick
Patrick suggests using Subversion as a way to manage and synchronize your home directory between multiple machines. The benefits of such as strategy is it allows for version control of your documents and the ability to keep them all in order no matter what computer you’re using so long as you’ve got internet access in order to grab your latest repository copy.

The actual functioning of Subversion was outside the scope of this discussion, but if you’re looking for information go to the Subversion website.

Patrick mentioned that if he could restart his method from the beginning, he would actually set up a few separate repositories. For example, separate ones for:

• /home/patrick/etc
• /home/patrick/bin
• /home/patrick/lib

The benefit of having separate ones being less customization to do because if you have only one there’s going to be a number of files/directories you’ll want to exclude for various reasons.

Patrick has also created a custom Makefile — allows him to run specific custom commands in his home dir (e.g. make test). In the makefile he has a “test” function that runs some basic commands to display the following.

your home is /home/patrick
your uname is linux
date is 20080225174525

Patrick uses the Makefile for scripts he’s written over his lifetime that does something he wants. When necessary, he can add new basic commands to the script to give him new functionality from the command line. Recently, he’s had people bugging him to start using Twitter so he added a new “tweet” function to his makefile.

Because he has his Makefile and all his other scripts in Subversion, he can use them wherever he wants. Desktop w/ linux? Checks out his latest code from Subversion. After creating and editing new files, synchronize to a web host to make sure the newest files will be available from his other machines. Then when the laptop needs to get the latest files, he does a checkout from the web host and now he’s up to date again.

Suggestions from others: Jdugan recommends using Mercurial — fewer dependencies than Subversion. Someone else suggested creating a /home/user/tricks folder that includes any scripts acquired w/ useful functionality and checking it into a repository to take your scripts anywhere with you.

Patrick’s Makefile:
Download It Here — Please note that the bottom portion of the text file should actually be put into a separate file in /home/username/etc/Makefile.linux

Hosting: If you don’t have a web host where you can host your subversion repository, its usefulness will be slightly more limited. Personally, I recommend Dreamhost — easy host to deal w/ and Subversion is a quick install (to svn.example.com) — but there are plenty of other good hosts as well, feel free to recommend some in the comments.