Summary: |
A CMS implemented on top of the Content Repository |
Description: |
CMS is a full featured content management system implemented on top of
the content repository which supports workflow, composite objects, dynamicly created attributes, publishing to
the filesystem and categorization. The user interface needs a great deal of work and the package relies on
acs-workflow which has been deprecated. Alternatives include etp and bcms (which is a work in progress), CMS
remains the best place to look to find examples of how the content repository should be used.
|
Maturity: |
New Submission or Maturity Unknown |
This package depends on: |
acs-content-repository acs-kernel acs-mail acs-tcl acs-templating |
Packages that depend on cms: |
cms-news-demo |
Package parameters: |
- ClipboardFloatsP
- Determine whether the clipboard should be in its own floating window. (default 1, type number, scope instance)
- publishing: PageRoot
- All items will be published to the filesystem with their URLs relative to this root. Relative paths are relative to [ns_info pageroot]. (default ./, type string, scope instance)
- publishing: PublishRoots
- The directories to which content is published as a space separated list. Relative paths are relative to parameter PageRoot. (default ./, type string, scope instance)
- publishing: StatusSweepInterval
- The interval, in seconds, between the sweeps of all items. Sweeping discovers items whose publication status (live/ready/expired) has changed and takes appropriate action. Lower values increase the precision of the publishing/expiration dates but decrease performance. Changes to this parameter are effective only after a server restart. (default 3600, type number, scope instance)
- templates: TemplateRoot
- The directory to which templates are published. See the TemplateRoot parameter in the acs-content-repository. (default templates, type string, scope instance)
|