Source Control
As you start building out your custom design files, you want to make sure they are not just sitting on your local machine's hard drive.
Benefits Having some sort of source control not only keeps your files safe but it ensures that two people are not editing the same document at the same time.
This is especially important within larger based development teams. As with any SharePoint document, team members can check out these items and apply version control to them. I would recommend Visual Studio Team Foundation Server 2010 (TFS) for enabling version control on your custom branding files. TFS provides the following main features:
- Version Control: Allows you to check a document in and out, and easily track and manage your documents.
- Work Item Tracking: Allows you to track and document requirements, tasks, issues, bugs, and test cases.
- Build Automation: Allows you to schedule automated build cycles, and build and configure triggers for manual builds.
You can also get source control and version history on small branding projects when all of your support files are stored within the SharePoint style library. The next section describes the folder structure and file details for the files that support the default look and feel of SharePoint 2010.