[Content Deployment] Authering, Staging, Deploying

I found a nice article on it ( https://blogs.msdn.com/sharepoint/archive/2006/05/02/588140.aspx ) written by (Tyler Butler, Program Manager for WCM) and I’ll try to summarize here.

“Basically there is something called Content Deployment which supports multi-topologies and its main purpose is enabling Authoring and Staging. The main idea here is Content Deployment usually goes from site collection to site collection. Through the “Central Administration Site”, Content Deployment can be configured to run and to be monitored. So you create a Job Object which is – an object that holds information of the contents needed to be deployed and a schedule (time and recurrence) – and associate a Path Object with it which is –an object contains source, authentication methods and distention. You can associate as many Jobs to a Path and the Content Deployment will deploy whatever changes were made since the last successful deployment even the dependant packages and layouts will be deployed too . The interesting part is having something called “Quick Deploy” which can be enabled on a job and then it will give the site owner to deploy a site instead of being the job of an administrator. Finally, a custom deployment can be written using the APIs.