As an Administrator or Developer, your daily experience using Cascade is drastically different from what simple users within your organization experience; and as your fellow employees have become more familiar with Cascade and its functionality through using the system, they have undoubtedly become enthusiastic about the nearly endless possibilities for content creation, management, and publishing with their CMS. Accordingly, the number of users, departments, and areas of your business or organization using Cascade’s “Publish” feature has grown. While there are several different ways to accommodate this growing number of users seeking to publish content in the system, the most fundamental way to create a more efficient publishing process for your business is to make use of Cascade’s Publish Set functionality.

Much in the same way that your Marketing department seeks to make information about your company readily available to prospects in a transparent way, it’s imperative that Developers seek to accomplish this same goal, but for an entirely different audience.

As a Developer or Administrator, you are likely familiar the variety of goals your organization utilizes Cascade to accomplish. Whether it’s publishing press releases in your Marketing department, university professors updating course catalogs, keeping news feeds current, or providing a wealth of descriptive information about your business and products, you have a variety of Cascade users utilizing the system to perform a variety of different tasks. 

Your fundamental knowledge of the system and which assets must be published in what order give you an extra insight into the software that can ultimately aid you in making your company’s publishing process more efficient. Publish Sets are components available in the Administration area of Cascade and allow you as a developer or administrator to specify groups of assets that relate to one another to be published on-demand or according to a specified schedule. These publish sets can contain files, folders, and pages.

As an administrator or developer, you have likely run into several cases in which a business or “simple” user needs to publish a page, but is unsure as to which pages need to be published along with it to ensure all relevant content is updated.  For example, if a user creates and publishes a new press release, all pages that link to the new press release must also be published. Because these users are not exposed to the smaller, more technical elements of Cascade, often times when they need to publish a page, instead of trying to determine which assets to publish along with it, he or she may just publish the entire folder to ensure all content is updated.

While this may be fine on an occasional basis, as the use of your CMS expands and Cascade is accommodating more users, you may find yourself in a situation where multiple users are publishing multiple entire folders at once. When this happens, it may be difficult for content that is of the upmost priority to be published in a timely way, as the publisher will be overloaded publishing multiple entire folders.  Because you have a different insight into Publish Sets and which groups of Assets must be published at once, it is up to you, as an Administrator, to ensure that your Publish Sets are constructed in a way that will maximize the efficiency of your CMS and its publishing functionality.

For more information on Publish Sets, and how to best construct them, please visit our Publish Set Knowledge Base page.