Learn about the typical (suggested) workflows for the initial setup, customizing, and maintaining the CMS.
After the CMS has been installed, administrators should set up and define the following pieces of information before proceeding. This workflow has been designed to streamline the process. However, you can complete the steps in any order, with the exception of finishing the Content Type Definition, which requires defined workflows, lifecycles, templates, and so on.
For more information, see Chapter 2 Terminology and the appropriate step-by-step procedures in this Administrator Guide.
Typical Workflow for Initial Setup
Assign staff roles
Default roles include Alert Recipient, Author, Editor, Manager, and Publisher.
When creating a role, add the name, description, and privileges for that role. Users assigned to the role will be able to only do those things they have permission for, such as creating new items or publishing. The Alert Recipient role does not have any privileges.
Add members (users) and administrators, if desired, to each role. When the role is assigned to a task, associated users are automatically assigned at the same time.
Refer to Section 4.17 Users, Groups, and Roles for more conceptual information.
Create workflows
The default workflow is called "Production Workflow," which includes tasks for Authoring, Approval, and Deploy.
When creating a workflow, add the name and description, then add the tasks. At that point, you can assign users and add roles. (If you assigned users to roles in the previous step, those users will be assigned automatically.)
For the workflow to be available, you must assign users or roles to at least one of the tasks. Otherwise, you will not be able to apply it as a default workflow.
Refer to Section 4.17 Users, Groups, and Roles and Section 4.18 Workflows for more conceptual information.
Add lifecycles
The default lifecycle is called "Simple Publication," which includes one phase with no delay that lasts forever.
When creating a lifecycle, add the name and description, then add the phases.
Refer to Section 4.17 Users, Groups, and Roles and Section 4.11 Lifecycles for more conceptual information.
Verify and customize templates
The default templates are alternate, public, and summary.
When the CMS is installed, all three are identical. You will probably customize one of the existing templates to create a new template. Customizing templates requires a programmer or graphic designer. You can upload a new template via the user interface and publish it, then assign it as the default to the content type or content item.
Refer to Section 4.15 Templates for more conceptual information.
Verify and modify the content type definitions
The default content types are Agenda, Article, Event, Job, Legal Notice, Minutes, MultiPartArticle, NewsItem, PressRelease, and Service. Each is delivered as a separate package and the appropriate ones will be installed with the CMS.
You can add child content types through the UI. When creating a content type, add the name, description, parent content type, default lifecycle, and default workflow, then assign the appropriate template.
Refer to Section 4.6 Content Type for more conceptual information.
Assign permissions to roles, users, and groups
You can assign each of these different permissions. Users inherit permissions from their groups and groups inherit their permissions from their roles. You can assign individual users different permissions from their groups or roles to cover special circumstances (for example, you can assign permissions to a user who is an author, editor, and publisher without assigning the user to a specific group or role).
Groups can be a subset of roles or can be defined through the /admin in Web Application Framework.
Refer to Section 4.17 Users, Groups, and Roles for more conceptual information.