web site source control

Hi, We have quite alot of source code to look after for our web site now, and I'm looking at putting it all in a CVS repository. Being new to CVS I am unsure of a few things. I thought I would ask you guys on this list how you go about source control for websites. Do you bother with a source repository at all? It has become a logistical nighmare keeping files in sync on development and production machines, especially since we have more than one programmer as of recently. Also, one of our editors sometimes changes a few PHP files because they contain content - that is the other problem, there is no clear divide between content and code, so how do I decide which files should be in the repository? I don't want to put files in which the editors need to change regularly because there is no way I will be getting them to check files out of a repository, that would be way beyond them. So, how do you guys tackle these problems? thanks, - Kev