Composite C1 comes with a http handler that generates an xml sitemap based on your page structure. This works great for most sites. If you have added any data driven sections such as a product catalog or blog, the default sitemap will need updated to include your new pages.
Working in CMS systems can be great, until you want to deploy some changes. Composite C1 is no different, the dataMetaData and workflow files can cause issues if you blindly blow them away, especially if your different environment’s databases weren’t sync’d up before making changes.
I’ve been testing some different deployment options the past few weeks and finally ended up with something I’m happy with. These builds aren’t currently automated, although if things go smoothly the next few months that might be the next step.
Updating a CMS based website can be challenging, there often isn’t a clean way to get local changes out to the server.
The easiest thing to do is push all the code and restore your local database on the server, but that won’t always work. For example, if someone will need to be updating content during the development process.
Today we’re going to look at how to deploy some of the commonly used elements in Composite C1 using the sql server data provider.