WiscWeb CMS - Site publication settings

This document explains how to use Site Publication Settings in the WiscWeb CMS.

Within the CMS, there are multiple components to set up publishing. In this section, we will take a look at some of the components in order to better understand how they interact, but will not include great detail on how to replicate them.

Publication Structure

Access at Administer Project Settings > Project > Publication Structure

Publication Structure link in SmartTree

The Publication Structure defines the folders that will be created on the server, to push the CMS's files to. In the example case in the screenshot:

  • the "documents" folder will be created to contain any documents that a user uploads, such as PDFs and Word docs (but the associations will be set up in a later step);
  • the "images" folder will be created to contain the CSS images and regular images in the project;
  • the "pdf" folder will be created to contain all PDF versions of the pages; and
  • the "print" folder will be created to contain all print versions of the pages

It is possible, though, to set up other folders as well, such as if you wanted to create a different "images" folder for each group in your project, so that there would be no chance of overwriting one another's images.

Publishing Targets

Access at Administer Project Settings > Project > Publishing Targets

Publication Targets link in SmartTree

The Publish Target(s) hold the connection information to the server that the CMS should connect to in order to publish its files. There might be one, two, or multiple Publishing Targets. Typically, however, there will be two Targets: one for the production site, and another for a testing version of the site.

Project Variants

Access at Administer Project Settings > Project > Project Variants

Publication Variants link in SmartTree

The Project Variants define the types of information that are published out: often times there are the regular HTML files, then Print versions of those files, and finally PDF versions of those files. Also, because we typically have two Publishing Targets (one for production, one for testing), we will often have two variants for each type of information published out, altogether resulting in the following variants:

  • HTML
  • HTML-testing
  • PDF
  • PDF-testing
  • Print
  • Print-testing

Each of these variants will be assigned to one of the Publishing Targets set up prior. As an end result, users will be able to select which of these variants are published. You might also see "Draft" variants that can be published, but you can ignore these, since they would include versions of pages that are still incomplete.

Publication Package

Access at Administer Project Structure > Project > [[Site Name]] Publication Package

Publication Package link in SmartTree

A Publication Package in the CMS pulls together the prior components, allowing an Administrator to define how each of the available variants should utilize the targets and structure available to them to get files to the right location. As you can see from above, a Publication Package is typically assigned to the structural element that the homepage is linked to, resulting in the entire site falling under the umbrella of this Package. However, it is possible to set up various Publication Packages for a given site, so that some files could go to one target, and some files could go to another target.

Regularly Scheduled Publishing

If you would like to schedule publishes to happen at regular intervals (e.g. to publish the website on a weekly basis), the CMS can do this via "publishing jobs." Please let the WiscWeb team know that you would like to accomplish this, and we can help set it up for you.




Keywords:wiscweb cms wisc web content management system site publication setting settings changing change edit editing structure targets variants package   Doc ID:12957
Owner:Ryan H.Group:WiscWeb CMS
Created:2009-12-27 19:00 CDTUpdated:2014-12-02 12:34 CDT
Sites:DoIT Help Desk, WiscWeb CMS
Feedback:  0   0