This likely applies to other serialization solutions as well, but I'm specifically using TDS in this case.
Here is the scenario:
- A site is developed and has gone live with some baseline content. This base structure is in TDS.
- Content authors have made edits to content items (as they do with a WCM).
- Meanwhile, development is being done which adds new fields to templates, potentially restructures pages with new renderings.
- Now this new development needs to be deployed without overwriting content changes.
Typically you will configure your Deployment Properties in TDS so that your production packages do not include items "owned" by content authors. But what about cases where new functionality requires introducing new content, or structural changes to existing content?
Is there some sort of best-practice workflow with Razl or TDS that can help with this? It just a matter of syncing production content and having a content "freeze" prior to deploying the new functionality?