Person(s) in charge of maintaining the overall settings for CMS. Administrators create roles and users, assign permissions, and define content types, templates, workflows, and lifecycles.
Email messages sent to assigned users when published content expires (exceeds its Duration date) or when tasks are completed.
Stage for a content item that indicates that it can be published. Only specific roles or users have permission to approve content items.
A method for preserving previous content items, enabling you to rollback if necessary. You can view the differences between versions.
Object that you can use to add content to the published webpage, including image and files.
Fields that help to define individual content items, found under the Basic Properties Authoring Step.
Role assigned to users who can add content to a content item, following the process defined by the administrators. The default process usually includes selecting the item type and folder location, assigning a name and title, defining the attributes and content, and categorizing the content. The content item must be approved before it can be published.
User interface (UI) that lets administrators and users create specific content items. The UI can be customized programmatically to meet the needs of your company.
Way to organize content items for easy searching by viewers. The CMS uses a category tree that includes categories, subcategories, and content items.
A subentry within CMS.
Information in a content item, which can include text, graphics, hyperlinks, and file attachments.
Portal for the CMS, providing access to the different content sections, public sites, and content items.
Individual "packets" of information that have their own workflow, lifecycle, and template, which are controlled by the content type. Content items are assigned default parameters for their type when users first create them.
Software that enables administrators and users to organize and track information.
Database that holds all information in the CMS, allowing for content re-use, version control, and more.
Self-sufficient unit of organization for content that acts as a sub-site. Different content sections can have different administrators, users, viewers, workflows, lifecycles, categories, and content types.
Defines attributes and hierarchy of content items. Administrators and programmers can create new content types, called UDCTs (user-definable content types). When administrators create new content types, they are children of the existing content types (address, agenda, article, event, FAQ item, file storage item, glossary item, job, legal notice, minutes, multipart article, news item, organization, press release, or service). Programmers can create parent and child UDCTs.
Publishing new content items to the website.
Role for users who can make changes to an existing content item. Users who want to make edits must have Edit Items privileges.
Indicates the date when the content item will be removed from the viewable area of the CMS.
Third (and final) step when producing a content item. Once a content item is finished, no further edits can be made and it can be published to the public site.
A way to organize input from viewers, such as name and address.
Way to categorize users and other groups under roles. Groups must be created programmatically in the Groups Administrator interface in the Web Application Framework.
Once groups have been created, administrators can assign permissions to them, which are inherited by the group's users. Administrators can create groups of groups. See Roles.
List of all changes made to a content item since it was originally created. The History list lets you analyze and track changes over time, and rollback earlier versions when necessary.
Folder that is displayed when a user enters the CMS. Users get to choose their own home folder. Administrators can reset a user's home folder to none when necessary.
Technology for controlling the content of a webpage through the use of servlets. JSPs call a Java program that is executed by a Web server. The CMS creates JSPs for the public sites.
Refers to the organization of a website's structure and content, helping users find the information they want.
Installation of a separate CMS within the Content Center. Each instance of a CMS has its own permissions and privileges, workflows, lifecycles, and content items.
Words or phrases that identify the content item during searches.
Defines the start and end dates of a content item. The default lifecycle publishes items immediately, with no expiration date. Administrators can control the lifecycles of all content items.
Preventing other users from being able to make changes to the content item.
Technically, "data about data." Metadata lets you further categorize content items.
Term applied when more than one user can access the repository at the same time, making edits to those pieces where they have the appropriate permissions and privileges.
Entry in the CMS at the root level of a hierarchy.
Another way to refer to "users or groups."
Portable Document Format. File format created by Adobe® and viewable on different platforms with Adobe's Acrobat® Reader®.
Set to allow or disallow specific actions, or privileges, by users when creating, modifying, or publishing content items. Permissions can be assigned to a role, group (if it has been created), or to individual users. Permissions consist of a user (or party), a privilege, and an object.
Named ability to perform certain actions, such as "read," "write," or "delete."
Makes a content item publicly viewable on the website.
See Content Repository.
Using an object more than once within the CMS.
Defines what actions users have permission to perform, such as authoring, approving, or publishing. CMS includes four default roles: Author, Editor, Publisher, and Manager. Administrators can create other roles as necessary.
RDF Site Summary. RSS provides a method for making Web content available for distribution or syndication to users.
Isolated instances of CMS that can be running at the same time. Sections provide a way to further subdivide content within a company.
Way to preserve the integrity of the information in the CMS by allowing only certain users to access specific areas, create or edit new content items, and more.
Indicates the date when the content item will be displayed to the Viewers of the CMS.
Files that describe how the information in the content item is to be displayed in a browser.
Individual steps that are assigned to specific roles or users as part of the workflow of a content item.
Settings that control layout, styles, and more to preserve consistency across the website.
Releasing a content item so that others might make changes to it.
Members assigned specific tasks and roles.
Tracking previous editions of a content item, allowing rollback to previous versions.
Those who are allowed to see the end results of the CMS. Administrators can specify eligible viewers as Public or Registered Users, or specify any groups that have been added. Content is only visible to those who are members of the Viewer Role. By default, the CMS assigns all administrators to the Viewers Role.
Defined series of steps, or tasks, that are required to create a content item, which allows administrators to assign specific content item types to specific roles or users. Administrators can create new workflows with additional or different steps to satisfy the needs of your organization.
Extensible Stylesheet Language, used to describe how XML (Extensible Markup Language) documents should be displayed in a browser.