According to Ashley Friedlein, for your content producers to feel like they are a part of the CMS when

creating content, it should connect with authoring tools highly and offer content capture interfaces. But
the technology just facilitates the content's collecting; it does not produce it ( Friedlein , A., 2003).

CMS is mot

- An authoring tool for a text, graphics, video, or audio manipulation but it manages the content
that these authoring tools create.

- A tool which automatically structure and organization the content

- A transaction processing tool but can manage the product and pricing information as well as any
other elements of content the user experiences in the online transaction process

- An analytics platform but typically work with other analytics tools to meet reporting and analysis
requirements.

- Only a publishing tool but it also collects content

The CMS does

- Collect
o Authoring : A CMS can help provide an authoring environment as well as input
templates and workflow to facilitate the authoring process.
o Syndication in: buy in content from external to be well structured
o Reformatting and other processing: Structure needs to be added to the content or
remapped to fit the existing content model, and unnecessary data of it must be
discarded.
o Creating content objects: Content in a format is added to the CMS as content objects.
o Adding metadata: the necessary metadata is added to the created content objects to
manage them within the system and publish them to users.
- Manage
The manage part is about storing and managing the content once in the system as well as
administering the system itself.
o Storage: all the content stored in a central repository is database system that itself
contains or references other content databases and files.
o Versioning and rollback: CMS provide Version control which is very important both in
ensuring that content creation and editing processes run smoothly in need of retrieving
the previous versions of contents. Also, rolling back is important to previously known
good versions of it or back to a particular point in time
 o Archiving: Content objects can prioritize to be archived on the CMS itself.
o Search and retrieve: Access to content is provided by search, browse, and indexing
facilities that work on both the content itself and any associated metadata.
o Integration with other systems: internal or external systems may take content, data, and
information from the CMS or feed it in.
o Workflow: Within the management part of the CMS, a workflow module is available to
set up, configure, and manage them by being able to apply different workflows to any
content object or set of content.
o System configuration and administration: managing access levels to the system and
security via logons and passwords; logging system activity; storing software
configuration settings and registries; maintenance routines, scheduled tasks, and scripts;
and performance monitoring to check that all the elements of the system are
functioning as expected.
o Link management and validation: a link-checking tool is provided to validate for internal
and external links which might be created dynamically by the CMS to ensure the links
are valid or be hard-coded into the content.

- Publish

The publish part is about getting content out of the system to suit target user, publication,
platform, and channel requirements.

o Deployment: Deployment refers to the processes and practices involved in moving

content from as a development or staging server to the live environment.
o Templates: The publish part of the CMS contains the templates that bring together
content and presentation elements to create the end publication for the user.
o Syndication out: buying in content to syndicate content out sharing the content with
other parts of the organization that can use it in other systems.
o Replication to/integration with other systems: Integration with the management part of
the CMS gives access to the “heart” of the system, the content repository and all that it
contains.

Reference:

Ashley Friedlein, in Maintaining and Evolving Successful Commercial Web Sites, 2003, Retrieved from
https://doi.org/10.1016/B978-1-55860-830-6.X5021-7