From past experience as a guest or part of the wedding party, we discovered it was helpful to have a site.
I had been fortunate enough to know the entrepreneurial woman [Adrienne McAdory] who purchased the rights to the new domain extension "dotWED". I was helping her with her publicity campaign and as a gift, we received one of the first dotWED extensions.
McAdory’s vision: lots of engaged couples want their own wedding sites, but the addresses they want aren’t available because other couples are already parked on them. Through the .wed domain, couples could purchase an inexpensive address — MarkandJessica.wed — for two years, long enough to see them married. After that, the site’s cost would drastically increase, pricing the couple out, leaving the space open for a new Jessica and Mark.
http://www.washingtonpost.com/lifestyle/style/move-aside-com-wed-other-domains-will-make-internet-more-crowded/2013/08/05/b389ca0c-fa21-11e2-9bde-7ddaa186b751_story.html
When the time came to build the site I was excited to make sure that it was easy to navigate and clear to understand. Not many website platforms allow users to change the URL, so in order to utilize my dotWED extension I had to choose from a limited list of providers. I decided to use www.WeddingWindow.com they had the least bland host templates.
Building the site was easy, the platform was basic and clear. At this point my only issues were quality photographs to populate the site. I had a folder full of selfies and vacation photos but the quality was low and the images were pixilated. We needed to have professional photographs. This was a problem because my fiancé hates taking photographs let alone posing for an entire shoot. A challenge lay ahead...
