Silva Content Objects

  Meta::
  
    Valid for:  Silva 0.9.3, Zope 2.6.2, Python 2.1.3
    Authors:    kit blake
                Clemens Klein-Robbenhaar 
    Email:      kitblake+infrae.com
                robbenhaar+espresto.com
    CVS:        $Revision: 1.8 $ $Date: 2003/12/06 07:06:06 $

  Content types

    There are three types of Silva content objects: content that is
    versioned, content that is not versioned (dynamic content objects),
    and assets (images, binary files, and data sources). 

    Versioned content

      - **Document**: the basic unit of information in Silva, a document
        can - much like word processor documents - contain
        text, lists, tables, headers, subheads, images, etc. Documents
        can have two (accessible) versions, one online for the public,
        and another in preparation (editable or approved).

        - **index document**: these special documents are
          automatically created in every container, however they can
          also be manually created and deleted. They function as the
          standard 'index.html' of a normal web server, where a
          browser request for 'http://.../silva/foldername' returns
          the index. Otherwise they behave as normal
          documents. Frequently index documents contain some
          introduction or summary about the folder contents. They
          often contain a Table of Contents (see
          "EditorTab":EditorTab/) element. It is also possible to add
          an Automatic Table of Contents as the index object.

      - **Ghost object**: these are special documents which function as a
        placeholder for an object in another location (like an alias,
        symbolic link, shortcut, etc.). Unlike a hyperlink, which takes
        the Visitor to another location, a ghost object keeps the Visitor
        in the current publication, and presents the content of the
        ghosted item. The ghost object inherits properties from its
        location (e.g. layout and stylesheets). 

      - **Link object**: this object contains a hyperlink (URL) to any
        location on the web (including the Silva site itself). When a
        user looks at a link it automatically redirects the user's
        browser to the indicated site. The link will also appear in
        table of contents and other navigation, just like a normal
        document would.

      - **Custom object**: developers can create new content types
        which can be plugged into Silva. They can be turned on and off
        per publication (same as Silva core objects).

    Non-versioned content 

      - **Indexer**: Indexes can be created that function like an index
       in the  back of a book. References must first be marked by placing
       index  codes in text (these codes will also export to print
       formats).  Indexers cascade downwards, indexing all index items in
       the current and underlying folders and publications (note that it
       only indexes documents that are published).

      - **Automatic Table of Contents**: An automatic table of
       contents is a content object that just presents a table of
       contents, nothing else. The same can be accomplished by adding
       a document and adding a Table of Contents (TOC) element to it,
       but this is a quicker way.

    Assets

      Assets are not versioned, but can be either included in documents
      or linked to via hyperlinks. 

      - **Image**: web graphics (gif, jpg, png) can be uploaded and
        inserted in Silva documents.

      - **File object**: any digital file can be uploaded as Silva
        content.  For instance large files such as pdf docs or mpegs can
        be placed in a site. File objects have metadata as well.

  Content workspace

    The ContentObject workspace has various screens that allow you to
    manipulate characteristics of the object. You can edit it, or change
    its metadata, or perhaps approve/publish it. The content type
    determines which screens are available. For instance images don't have
    to be approved or published, so they don't have a
    "PublishTab":PublishTab/. 

    Each screen shows a 'view' on the object. A view is an 
    aspect or facet of one object. Thus the PropertiesTab shows the
    object's individual metadata (as opposed to the metadata of a
    container, which cascades down the hierarchy, being acquired by all
    objects below). 

    - "**EditorTab:**":EditorTab/ all editing operations occur here, such as
      text manipulation, image insertion, or file upload.

    - **PreviewTab**: in this screen a preview is displayed. If the content 
      is versioned, the latest version of the object is shown. If the
      content is a File Object, a link is provided (for testing). A Data
      Source displays the rendered dynamic content. For documentation see
      the container "PreviewTab":../ContainerObject/PreviewTab.

    - **PropertiesTab**: properties of the current object can be
      adjusted, such as metadata like subject and intended
      audience. For documentation see the container
      "PropertiesTab":../ContainerObject/PropertiesTab.

    - **AccessTab**: user rights and access restrictions for the current
      object can be managed (only accessible for Chief Editors). For
      documentation see the container
      "AccessTab":../ContainerObject/AccessTab.

    - "**PublishTab:**":PublishTab/ request approval for or publish the
      content object.

<br />
Copyright &copy; 2002, 2003, 2004 Infrae. All rights reserved.<br />
See also "LICENSE.txt":license.txt
