What's the best method for deploying changes to the actual DNN website?  Not worried about modules at all, but the entire website?

For example, I have a development environment, where the DNN install and database lives all on my local machine.  I then have a staging environment where I deploy updates and is only viewable by our internal business users.  My third environment is our actual production environment that is viewable and usable by our actual customers.  The problem I'm facing is, what if I add a page to my local DNN site (development environment) and I want to propagate that change to my staging environment (the internal site only viewable to my business users who are testing - NOT customers)?  And then eventially to my gull on production environment that is used by our custoers.  We use TFS for our code repository so I am familiar with branching and merging code, but I am wondering what is the best way to do that with regards to a DNN site.  Especially given that there is a database piece that goes with the DNN site. 

My goal is basically to have the entire portal in TFS - along with all my module code as well - across all the different environments.  I'd also like to have all of this in TFS so in the event of a catastrophic event, I can push out the code from TFS and get the site back up and running a relatively short time.  The best answer for the that might be a file system back up and seperate DB backup rather than something like TFS.  But what about propagating the actual website changes from environment to environment?  Or does it just need to be a manual process?

Thanks!