Perhaps it is a sickness, but I tend to plan trips, especially overseas ones well in advance. That gives me the security of knowing that I can book what I want, when I want it. It gives me the luxury of having plenty of time to plan, to optimise, to replan...
It also means that I have MORE THAN A YEAR to wait for the ride, so to alleviate some of the boredom this is likely to turn into the best documented Italy trip ever :-)
To go back a few years, here is how our trips have progressed:
- In 2003 we visited Spain. This was the first of our web-documented trips, with a dedicated, hand-crafted web site and photo storage after the event on Flickr.
- 2004 was Turkey. There wasn't much planning to do (a bus tour) but I did blog the trip and collect my photos.
- 2006 was NZ (Central Otago) and there was a planning web site, once again hand crafted.
- 2008 and 2010 were in Italy. For each there is a wiki at PBworks, a blog at Wordpress and a photo set on Flickr. Note three different suppliers of free cloud resources: the best there were at the time.
- 2012 was back in Spain. By now my move to the integrated Google environment was started: the Blog was moved to Blogger to get better integration for photo uploading etc. from Android devices. However there is still a PBworks wiki and I still use Flickr as the ultimate photo repository.
So now it is time to plan for 2014 and the move to consolidate it all in the Googleplex is finished.
These already exist:
These already exist:
- The wiki at https://sites.google.com/a/
keogh.net.au/apennines/ which is the "knowledge base". Everyone who "signs up" for the trip can modify these pages. - The blog at http://apennines.blogspot.
com.au/ which is a narrative of the planning and the trip itself: my view of it. - A Google+ page at https://plus.google.com/
117699810052162622303 which may well end up as the short term storage for photos. - All the document and file storage (.GPX files, insurance documentation etc.) in Google Drive.
- A Google Calendar to hold a day by day schedule.
No comments:
Post a Comment