But putting that info online has had another benefit: upcoming conferences want my bio, or a headshot, or a sense of where else you've spoken to convince the conference committee that you really are the guy they want to invite. Now I just have to give them a URL. In at least one case, I got cold-called by someone who was looking for a presenter on a topic I'd spoken about before, which ended up being a very fun presentation (well outside my usual focus) and one that they appreciated. Turns out that putting relevant content on the web can be useful for people looking for that kind of thing. Who knew?!
But last year I'd grown tired of the wiki app I was using (PmWiki) and wanted the CV in something more robust. I decided to give Google Sites a whirl - other than a few internal pages at Google, I hadn't used it much and it seemed a good opportunity to try it out. The CV was previously at http://www.rklau.com/cv/; the version managed by Sites is now at http://cv.rklau.com/ (and the old URL just redirects to the new one).
Advantages of having this managed by Google Sites:
- No software updating. I'm sure by last year was several versions behind. That's usually a bad idea - security vulnerabilities can lead to easy defacing of content, and your resume is the last place you want defaced content - but I just never made it a high enough priority to stay current. I was lucky - as near as I can tell, I never got hacked - but it was luck.
- Better editing interface. The WYSIWYG interface on Sites makes it much easier to add content without having to remember whether this wiki uses three apostrophes for a larger font size or the plus sign, and whether URLs are [URL|title] or [[title|URL]] or some other variation.
- CNAME support. Like Blogger, Sites supports hosting your content at a URL of your choosing. So I was able to set up http://cv.rklau.com/ and have the site immediately served from my domain.
- One less password. I had a separate username and password (managed by PmWiki, not the most secure approach in the world) to prevent anyone other than me from modifying the content. That's fine, until I lose the password, and then get locked out of my own CV! Having Sites manage the content means it's managed by an account I use much more frequently (my Google account), and can rely on Sites' much more robust notion of permissions.
The only downside to this system is that it's too much information. Nobody really cares about that speech I gave in 1996, or the magazine article I wrote in 1999. On my todo list is an abbreviated version of this page that's just the highlights... I'll get around to that. With Sites, moving the data around is a snap.