Publishing
Cascade Server has a robust publishing engine designed to bake the files out in the development environment and synchronize those environments with one or more production servers. The assembled content is transformed into native XML files, standard HTML, and/or .NET files (.aspx). The strength of this system is that upon the publishing of content, the information is completely decoupled from the CMS allowing it to operate independently in any standard environment.
The publishing process operates via manual user action, on a timed schedule, or via a workflow trigger. To manually publish the content, the user can click the publish button for the appropriate asset or group of assets (publish set). The production web server does not need any special software because content can be transferred via standard FTP or a mapped network drive. It is recommended to have the WCMS on its own server and acting as its own staging and development environment.
Changes can be published to the site immediately, and a full rebuild of the site is not required. Content can be published on demand and/or scheduled in a daily or hourly fashion.
