SharePoint’s content deployment feature is a great way to manage content changes, and very appropriate for public facing websites. However I do have three quick comments on the functionality:
- Binary changes – I’m aware these are not covered under the scope of content deployment, but I’ve had a lot of problems where people have deployed code to the authoring farm and not to production. Very frustrating when you’re trying to publish a change at 5PM on a Friday afternoon. I would like to see the practicality of having the ability to have these binary changes included with content deployment. Better release management would also probably help.
- Needs a farm admin to publish – I’d like to be able to delegate this to a business representative to run the publishing job (ad-hoc).
- Random publish failures – Sometimes, the publishing job just doesn’t work. Try again and all is well. If it is a timeout, it’d be great to see this automatically reattempt.