I am evaluating Orchard as a potential CMS for a rewrite of a very large and popular site and I am loving the Orchard technical design and overall approach so far. I am at earlier stages of evaluation so I will have a few questions to ask.
Site will be powered by 3 geographically dispersed datacenters with 15+ members editorial team constantly pushing content to live environment. Therefore editors will need automated means of pushing the content from their staging environment into
live servers (each running SQL Server clusters). What is the prefered approach that you guys can recommend or already implemented for this? Would you recommend replicating filtered data from staging to live using SQL Server replication?
The closest discussion I could find about Workflows is http://orchard.codeplex.com/discussions/241520. May I enquire about the current status of this?
Editorial team will need to preview the changes they made before publishing them. As far as I can see the only way to do that currently is to publish the content and view content directly on the site - I have installed the "Version Manager" module
to get preview functionality for draft content but widget layers are not displayed in preview mode (because widget URL rules don't match with the preview URL structure). Without workflow (and one stage in between draft and published), content that is approved+published
might get deployed together with content that is published for reviews, etc as both of them are seen as "published" by the system. What is your recomendation to solve this problem?