Publishing
Digest
Cascade Server features a robust publishing engine designed to bake files out in the development environment, and synchronize those environments with one or more production servers. Assembled content is transformed into native XML files, standard HTML, and/or .NET files (.aspx). Upon the publishing of content, the information is completely decoupled from the CMS, allowing it to operate independently in any standard environment.
FAQs
- Can I schedule content to Publish at a later date?
- Publishing can be triggered manually, through a workflow step, or on an automated schedule. Publish and expiration dates can be added to all content. If an expiration date is added, the user also has the option of selecting an archive folder that the page should be moved to upon expiration. This can be done at the content item level and at the collection (folder) level.
Concept
Publishing Content
To publish an asset, (page, file, folder, etc.):
- Select the asset to be published from the asset tree
- Click the "Publish" tab
- Check the boxes corresponding with the destinations you'd like to publish the content to.
- Click "Submit" to publish your content to the selected destinations.
Un-Publishing Content
To un-publish an asset, (page, file, folder, etc.):
- Select the asset to be published from the asset tree
- Click the "Publish" tab
- Check the boxes corresponding with the destinations to unpublish the content from.
- Click the "Un-publish" radio button:
If your un-publish request was sent successfully, you will see a notification similar to the one displayed below:
FAQs
- Can Cascade Server automatically Publish and Retire content on a Schedule?
All content can be posted and expired at predetermined times. When creating or editing a page, users may simply edit the metadata fields indicating the start date, expiration date, and which folder (if any) the content should be moved to upon expiration.
This is a great way to automate the management of time sensitive information. Coming events, for example, can be automatically removed after the event has passed.
- How does Cascade Server tie into a Web Server?
- 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 any scripting language desired. The strength of this system is that upon publishing of content, the information is completely decoupled from the CMS, allowing it to operate independently in any standard environment. Single points of failure such as database connections and third party servers are mitigated as the content has been “compiled.”
- How does Cascade Server support Secure Publishing?
- Cascade Server supports secure publishing through the use of industry standard secure transport methods such as SFTP, and VPN. The organization may also implement the secure transfer utility of their choice.
- Can Cascade Server be used with Multiple Web Servers?
- Cascade Server supports secure publishing through the use of industry standard secure transport methods such as SFTP, and VPN. The organization may also implement the secure transfer utility of their choice.
Related Links
- Assets
- Page
- Opening a Page
- Creating a Page
- Editing a Page
- Previewing a Page
- Publishing a Page
- Moving a Page to a Different Folder
- Creating a New Page From Default Asset Factory
- Creating New and Custom Pages Using Asset Factories
- Copying a Page
- Editing a Page in Cascade
- Publishing a Page in Cascade
- Creating an Index Block for a List of Recent Pages
- Page Layout and Rendering Behavior
- Production Server
- Publish Set
- Publisher
- Staging Server
- Workflow Trigger