Maybe at some point I'll try FileHamster. It looks promising, and it's geared toward web designers and developers.
For a long time - I'm talking many years - I've wanted a version control system for my files, even something as simple as a word-processing document. For example, when I was working on an essay or a resume, I had to make many revisions to it and often revert back to them, so I would end up with many different files, some with meaningful names and some without, and I would be left to rely on memory, those titles, and the "Date modified" property of the file to pick the right revision.
It's finally time to start doing things right. I just started using SVN through the TortoiseSVN Windows client.
Most of the tutorials and blog posts I found on running it locally presume that you're starting from scratch, i.e., you're embarking on a new project with zero files right now. I, on the other hand, would like to be able to version control existing projects. Secondly, they presume that you only have one project going at a time, which is probably not true for most developers.
Thankfully, the procedure is pretty much the same with existing multiple projects. What you need to do differently is create subfolders inside the main repository folder, and import the existing files from their current location into their corresponding repository subfolders. From there it's business as usual: checkout > edit > commit.
I still have to read about the more advanced features like merge, switch, and branch. The software comes with great documentation, along with a link to the free online book on Subversion as a system and concept.