My question is: what is best practice for working in a team of developers, sharing code using source control and SF Thunder, and then deploying to staging and live servers?
How does Sitefinity support source control
Sitefinity's structure fully allows you to maintain a full steam development environment and manage it through source control.
Let me elaborate a bit further on the source control story and development process with Sitefinity:
Sitefinity is a native ASP .NET web application and as such it supports the source control story that any other Web Application would – with TFS or any other source control system that you are using. Internally we have a very agile infrastructure and structure our entire code base and automated tests in TFS, maintaining a nightly build infrastructure etc.
But when it comes to the question of best practices, I would probably like to take a look at a few of the Sitefinity-specific elements and features that relate to source control, as well as give you an idea of the full toolset you have at hand for this:
Here is another useful blog post that discusses some of the practices that our major partners put in place. You can find useful tips and tricks there that could help you with choosing an approach of tackling your internal IT infrastructure. Here I’d like to note that this blog post is pre-Thunder and pre-Site Sync, so a lot of those processes have been improved since then, and continue to be improved with each release.
Thanks so much for taking the time to write this - it's very useful and has set us up nicely.
This is an excellent resource.
I'm curious if there have been any recent developments or changes to Sitefinity that would change the general concepts outlined here.