Currently our team (web devs, one designer and one copywriter) all work on separate workstations but do our changes on the same dev environment (we all mount the same shared drive), it’s a marketing site and not a web application, so no builds or deployments, we just push changes to the live site once they are done, but I think it’s important for us to keep versions of files, especially serverside code, even if it only makes up a tiny percentage of our content (mostly static pages).
I’d like to use version control for our work setup, but I’m not sure if SVN or GIT will play along with more than one person checking in/out from the same dev environment. I’ve got existing experience with SVN, CVS, GIT, Perforce and PVCS but have always worked with individual dev environments.
I’d like a solution that doesn’t require us to run separate dev environments as we lack the infrastructure.
Most, if not all, version control implementations are intended to be used by more than one person. Both Subversion and GIT will happily do everything you require but you might find Subversion easier to get up and running with quickly. If you intend to host it in a Windows environment, take a look at VisualSvn Server.
The major difference between GIT and SVN is that GIT is a distributed system whereas SVN relies on a central repository. In software development, there are good arguments for using a distributed system but the needs you describe would be easily served by the much simpler SVN implementation (I think).
Another good reason for using SVN (under Windows) is that the TortoiseSvn client is one of the best examples of a user interface to any version control system. It is extremely easy to learn how to use and well documented as well as supported by the OS community.
It may also be worth investigating the various providers of hosted version control systems if you don’t want the overhead of maintaining your own source control servers.