|
Overview
The following list of Engenda capabilities
is not exhaustive, but represents a sampling of features supported
by Engenda that we've seen requested by organizations investigating
CMS products.
Engenda supports:
Authoring
- Supports re-usable content components
- Separates content from design through the use of site templates
- Browser-based interface
- supporting access to CMS from Windows, Macintosh and UNIX
- User can edit content without HTML knowledge, including user-friendly
(wysiwyg) tool
- Interface supports multiple options for authoring, such as forms-based
authoring MS Word, MS Excel, WYSIWYG browser editing, any HTML
editor
- Forms-based authoring support, is easily tailored to fit the
editing needs for different types of content
- Forms-based authoring supports form controls such as drop downs,
text areas, WYSIWYG HTML formatting, radio buttons, insert / move
/ remove / sort content, check boxes, calendar pop-ups etc.
- Supports nested templates
- Multiple, convenient methods to find and retrieve content in
the CMS, including easy-to-use search interface, browse site-structure,
and browse by multiple navigation paths (such as by content type,
author, edit date, or any other meta-data field, whether custom
or standard)
- Content is accessible from various navigation paths, based on
the content's tagging
- Can create a copy of an existing asset (page, content component,
template etc) on which to base creation of a new asset
- Automatically fills-in standard metadata when available (e.g.
author, created date, status)
- Allows user-specified metadata to be provided during authoring
- Can support association of assets to each other
- Users can specify metadata field values from a limited vocabulary
- Provides a brandable interface for remote authoring
- Templates can be created using standard development tools like
Dreamweaver
- Can associate content with alternate templates
- Can process templates using component page model to produce
a static site or dynamic site
- Server-side code such as ASP, Perl, JSP, etc., can be included
within a template
Publishing
- Supports publishing using any site delivery technology, including
different web servers, application servers, ASP, JSP, PHP, etc.
- Can support any preferred process for multiple development,
staging and production servers. Users can preview different versions
of site to test look-and-feel, ensure proper content placement,
etc.
- Can publish content to one or more Internet, extranet or intranet
Web servers
- Ability to preview rendered page prior to making changes to
live site, including dynamic pages that execute code, pages that
include external content, ASPs, JSPs, etc.
- Provides mechanisms to transform content from one format to
another
- Supports static HTML and dynamic sites. Supports hybrid sites
(static, dynamic, content-push, content-pull, different app servers)
- Can use Engenda as pure back-end CMS, and publish to your preferred
method of live site delivery
- Alternatively, can use Engenda for both back-end CMS and live
site delivery, using Engenda's built-in application server
- Allows scheduled launching and automatic expiration of content
on the site
- Can maintain separate expiration and purge dates, allowing expired
assets to be re-upped
- Rollback to earlier versions of site pages or sections. Can
rollback in batch, incrementally, or as part of a workflow action
- Can produce automatic generation of navigation in a variety
of flexible ways
- Can produce automatic set of links to related content based
on meta-data and full-text search
- Internationalization features. Support for publishing of multi-lingual
language pages
- Server side code such as ASP, Perl, JSP, etc., can be published
directly to a website
- Content from external sources (i.e. databases, file systems,
etc.) can be used by the CMS, and metadata can be associated with
that content
- Can integrate with ODBC/JDBC datasources
|
Workflow
- Flexible workflow engine that can accommodate multiple processes,
multiple sites
- Supports different workflows for different sets of content or
different groups
- Supports sequential and/or parallel workflows
- System verifies role or group-based access rights to perform
workflow actions (e.g. edit, delete, approve, publish)
- System verifies compliance to your rules prior to performing
workflow actions, such as verifying all content components inside
a page have been approved, or verifying that all sub-tasks are
complete
- MS Visio integration available to create and edit workflow
- Comments can be associated with workflow tasks or events
- System notifies users of tasks or other events associated with
a workflow via email
- Workflow tasks be routed in an ad-hoc fashion when needed
- Reporting tools to help track projects and tasks
- System can create projects, tasks, sub-tasks automatically
- Audit trail maintained for all workflows
Content Management / Content Repository
- Users' views of the content repository filtered so they only
see the content they can access
- Can create custom taxonomy of content
- Global search and replace can performed throughout the repository
- Supports check-in/check-out of content with locking
- Repository can store metadata and content, meta-data only (content
stored externally), and content only
- Stores multimedia assets
- Allows creation of custom asset types
- Can associate metadata with any content type, including different
meta-data fields for different content types. Can create custom
content types
- Allows for rollback of revisions
- Allows friendly, side-by-side comparison of two versions of
content
- Comments can be attached to content when it is checked-in
- Support for publishing several media types. Can upload and use
files in any format. Examples: PDF, HTML, images, sound and video
files, Flash, etc.
- Data import. Can import data in order to transfer current information
into the system in an easy way
- Data exchange with other systems. Can exchange data with the
other software systems that exist within organization
- Content transformations -- can transform content during upload
into the repository and during publication or transfer
Authorization / Permissions / Capability
Model
- Full control over which users can edit which content
- Users can be assigned to one or many roles
- Content visibility based on role / group / user
- Fine-grained user interface visibility. Can control which buttons,
dialogs, tabs, pick lists, etc. are presented to which users /
roles
- Integrates with LDAP
Other
- Supports Boolean search parameters, "exact phrase" and keyword
searching, "Advanced" search using fields of metadata
- Can specify portions of the site to search, as well as whole
site
- Can show related docs or similar information that relate to
search results
- Open/standard architecture (JAVA, XML, XSL, etc.)
- Easily accessible user help (e.g. online help)
- Highly extensible; developers can extend the existing functionality
using XML XSL, JAVA
- Supports logging of usage statistics
|
|
