[CMF-checkins] CVS: CMF/docs - CMFDocumentation.stx:1.1

[Michel Pelletier]

Update of /cvs-repository/CMF/docs
In directory cvs.zope.org:/tmp/cvs-serv24391

Added Files:
	CMFDocumentation.stx 
Log Message:
edits to cmf docs

=== Added File CMF/docs/CMFDocumentation.stx === (1448/1548 lines abridged)
The Zope Content Managment Framework

  Introduction

    Web sites today have become sophisticated, dynamic experiences
    that provide powerful services. At the same time, businesses want
    new ways to leverage brand and engage customers, usually on a very
    large scale. Yet with the explosion of content on websites,
    managing the daily flow has become a very expensive, brittle
    proposition.

    This is the market that content management systems (CMS) are ideal for. 
    The Content Management Framework (CMF) from Zope Corporation is designed 
    to solve these content management issues by delivering the following 
    benefits:

      - Superior speed to market for applications and content.

      - Dramatically decrease website staff workload by safe delegation 
        of content authoring.

      - Powerful searches using sophisticated organization of content.

    The CMF is designed as a framework of components for the Zope 
    application server. This approach to content management is "both buy 
    and build", as it delivers an extremely extensible foundation for 
    customization as well as providing useful tools "out of the box".

    In the CMF worldview, everything is content. This applies to 
    traditional things such as HTML pages. But it also applies to dynamic 
    information such as posts in a threaded discussion or calendar events. 
    It also means that images, dowloadable executables, logic in scripts, 
    etc. are also content.

    The goal of the CMF is to unify the management of content and apply a 
    suite of services. These services include cataloging, workflow, and 
    syndication. The CMF works hard to allow authors to use common tools
    such as Adobe GoLive, Dreamweaver and MS Office to produce content 
    by supporting standard protocols such as FTP and WebDAV. Specific tools 
    are not required, however, as everything in CMF can be done using only 
    a Web browser.

    <font color="red">Note - find more intro material to put here</font>


  Building and managing a CMF site

    Initial setup and design of a CMF site is performed by a highly
    privileged user referred to as the "Site Manager". The Site Manager
    is responsible for the overall configuration and organization of a 

[-=- -=- -=- 1448 lines omitted -=- -=- -=-]

    document does not go into detail on advanced development topics. 

    Advanced developers should visit the "CMF development site",
    http://cmf.zope.org for more information on resources to help site 
    developers with advanced customization.


  Glossary

    **Site Manager** -- The actor responsible for implementing site 
    policies such as security, workflow associations, metadata and 
    syndication policies. The Site Manager is also responsible for
    the overall organizational structure of the site.

    **Membership Manager** -- The actor responsible for managing who
    has access to a site (particularly back-end line of business 
    users), and controls the privileges and properties of users. 

    **Site Developer** -- The actor responsible for implementing new
    functionality for a site and making changes to existing site 
    capabilities. This is a "programmer" type of role, and users 
    acting the Site Developer capacity are technical people.

    **Add-on Developer** -- The actor responsible for implementing 
    new functionality that is suitable for distribution to one or 
    more sites. **

    **Site Designer** -- The Site Designer is responsible for producing
    and maintaining the "look and feel" of a site. This includes 
    graphics, layout, navigation and other human factors.

    **Workflow Designer** -- The Workflow Designer is responsible for 
    defining new workflows and customizing existing workflows to meet 
    business goals.

    **Content Creator** -- Content Creators are responsible for producing 
    and maintaining the actual content of a site. 

    **Reviewer** --  The actor responsible for ensuring the quality and
    correctness of site content.

    **Site Visitor** -- A Site Visitor is an "end user" of the
    site. The visitor may or may not have an identity known to the
    system. Visitors with a known identity are referred to as
    "Members" of the site, and often can do more on a site than
    visitors without a known identity ("Guests"). Member visitors
    often have a participatory role on the site. Site Visitors have
    some general goals that are applicable to most sites, but many of
    the specific goals and expectations of Site Visitors are dependent
    upon the specific CMF site.