I'm using a version control system, in my case CVS, but that's just because I happen to be most familiar with this one, and like being able to access the underlying files manually if needed. The main advantage of using a version control systems (VCS) to me is, that it allows (or even enforces) commenting versions checked in, so you'll know later on at which stage of work a certain version has been, and can select the version you may need for further development.
Also, most modern VCSs allow collaborative work, which may be of importance when you're working on a project together with a group, or want to give a teacher access to an early draft for correction, or a friend for proof-reading.
Which VCS doesn't matter as much as that it fits your style of work, and that you're comfortable using it.
VCSs are best at storing text-based files, where they can keep track of the differences from version to version. Confronted with binary files, such as bitmap images, they can usually do little more than store one blob after the other together with a timestamp and your manually provided version information. So, if you expect binary data to change often, they're not much of an improvement, and tend to fill up your data storage.
Given the resources you mention, it seems that you might be best off with something making use of your webserver, so it might be a good idea to explore which versioning tools you can use there. You don't tell if you're limited by scripting language, choice of database or other possible requirements, but there's a few wikis you might consider which also offer version control over text and attachments.
Things to explore include:
- WebDAV/DeltaV (WebDAV was supposed to be a "Distributed Authoring and Versioning" filesystem, unfortunately the "Versioning" Part of the Filesystem never got specified and didn't really catch on. Hence the concept was reworked as "DeltaV", problem being that there isn't much software around implementing it.)
- SVN Autoversioning being one of the few notable implementations getting near that goal.
- There's a MediaWiki planning to integrade WebDAV - You might want to check their status if your Webserver meets the requirements: http://www.mediawiki.org/wiki/Extension:WebDAV
- FosWiki is file-based, and applies version control to both wiki articles and attachments.
- If you don't mind giving your data to another site, LibreSouce (http://dev.libresource.org/) looks like a good example of what can be done on a webserver (found through an article comparing several VCSs, 7 Version Control Systems Reviewed)
So maybe there's something down that line for you.