Hello, I have just started to created my website using wordpress. This website is going to have very minimal development other than what wordpress already includes, some minor code changes I will be making, and perhaps later on outsourced code changes. The majority of the changes that will be made over time to this site will be maybe CSS changes and HTML changes. I am wondering if anyone has any recommendations as to whether or not it is worth incorporating version control when you are using wordpress? The versioning control will help a lot any time changes are being made, so I can see exactly what changes and perhaps go back to old versions if necessary. Unfortunately, however, I am worried that because wordpress plugins or because of the way that wordpress works, it will periodically modify perhaps dozens of files at random times all of which would need to be checked out under version control (or else they would fail to get modified, maybe causing errors if they had to). Does anyone know if versioning and wordpress will mix ok? Has anyone else used versioning and wordpress? What are other people using for web site source control? (If at all). Thanks.
Why exactly do you want to include VC (Version Control)? There are only 2 instances where I would personally consider using it. A) If there are multiple people working on it at the same time or B) It is a big project which will be updated regularly. If you are the only one working on this project, I don't see the usefulness of it, unless of course you are releasing a product and may need to have older code stored in a repository in case you break something later on, but the idea is that you shouldn't complicate your development process more than you have to. If you feel its warranted for what you are trying to achieve, then look for a solution to integrate it, otherwise go without it.
Well, let's take a simple case. Let's say I change the CSS 20 times to get the footer of the website just perfect. Well, maybe a little bit down the road I don't like it anymore and would like to revert back to some point along the way. Or maybe I just want to change things around within the site at some point. This seems like a very common thing, and if I don't know what the CSS was before, or the layout for example, it is going to make going back to a previous version a total pain.
Well in this case you probably do want to take advantage of some kind of VC to keep a record of your changes. However, in regards to your question about it being a pain, I don't believe it should be. Since all the website templates are stored within .php and .css files just like a normal site is. So it would only be a matter of making the changes and then uploading the updated files to overwrite the existing ones in the theme folder.
Correct @ GWiz Using VC to revert changes is useless. If you are not able to code CSS... get someone who is. Doing CSS changes is done in minutes.