Site Manager Documentation
  
  Meta::
  
    Valid for:  Silva 0.9.2, Zope 2.5.1, Python 2.1.3
    Authors:    kit blake
                Clemens Klein-Robbenhaar 
    Email:      kitblake+infrae.com
                robbenhaar+espresto.com
    CVS:        $Revision: 1.9 $ $Date: 2003/05/18 22:12:50 $

  This document describes the workings of Silva from the point of view of
  a (Silva) Site Manager role. This role has the same rights as a Zope
  manager.
  
  **Subdocuments** --
    "TemplateDesign":TemplateDesign/ <br />
    "Silva Services":SilvaServices/ <br />
    <br />
  
  Assumptions --
    The reader is assumed to have an up-to-date browser (Mozilla /
    Netscape 6+ or Internet Explorer 5+ or similar), and be conversant
    with Zope.
    
    For the purposes of locating objects, the Silva installation is
    assumed to be 'default', where Silva is installed at the
    root level of a Zope instance, and named 'silva'. All paths in this
    document begin with '/silva'.
  
  Nomenclature -- 
    ZMI refers to the Zope Management Interface. SMI refers to the Silva
    Management Interface (where Authors and Editors work). A ZPT is a Zope
    Page Template.
  
    To limit confusion, we rarely use the word 'user'. Silva
    has several built in roles (Author, Editor, Chief Editor, Manager).
    These are always spelled with a capital letter. When we refer to the
    person or organization which has installed Silva, we use the word
    'customer'. A person viewing public pages (anonymously) is
    a Visitor.

  General
  
    Welcome to Silva on a managerial level. Let's start with a few tips
    which are good to know.
  
      - If you're logged in as a Manager, the breadcrumb trail contains
        an extra link: '/manage...' that takes you directly to the Zope
        'manage_main' in that location. The access key alt-. initiates
        the action immediately.
  
      - In the ZMI, the second tab is called "Silva /edit..."
        and that takes you to the SMI at the current level.

      - A few key aspects are defined in the Silva root. See the <a
        href="#properties">Properties</a> section below (e.g. to change
        the help link in the tab bar).

  Objects and Services in the Silva root
  
    In the ZMI, at '/silva/manage' or '/silva/manage_main', you'll see a
    number of Zope and Silva objects. What follows is a quick listing,
    with links to more information. Some of these items actually reside
    on the file system.
  
    Note that if Silva objects (publications, folders, documents, etc.)
    are present in the root publication, those items will be mingled in
    the listing as well.

    **Members** -- a Zope Folder containing information about 
    Silva members, i.e. Zope users which have been assigned
    a Silva specific role. Normally this folder should be left
    alone; the Member objects are created implicitly on demand. 
    removing Member object does not revoke the roles
    from the corresponding user, it only removes the additional information
    available via the "user settings" page of the SMI.
  
    **content.html** -- 
    ZPT that helps render public pages. See the 
    "TemplateDesign":TemplateDesign doc.
  
    **frontend.css** -- 
    Cascading Style Sheet that determines the
    typographical styles in the PreviewTab and public pages. See the
    "TemplateDesign":TemplateDesign doc.
  
    **globals** -- 
    This folder ('silva/globals') resides on the file system. It contains
    Silva user interface elements,  and will be overwritten in an
    upgrade.
  
    **index** -- 
    A Silva index document in the Silva root (or Silva
    'top', as it's called in the documentation for 
    AuthorEditorChief Editor). 
  
    **index_html** -- 
    A Python script that handles web requests. See the
    "TemplateDesign":TemplateDesign doc.
  
    **layout_macro.html** -- 
    ZPT macro that renders public pages. See the
    "TemplateDesign":TemplateDesign doc.
  
    **preview_html** -- 
    A Python script that handles Silva previews. Will
    be covered in the SilvaDeveloper docs.
  
    **rename-to-override.html** -- 
    ZPT that can be used to create custom
    pages. See the "TemplateDesign":TemplateDesign doc.
  
    **standard_error_message** -- 
    ZPT which displays an error message in Silva style (as opposed to Zope 
    style). 
  
    **standard_unauthorized_message** -- 
    ZPT which displays an unauthorized message in Silva style (as opposed 
    to Zope style). 

    There are a couple of Silva specific "Service" objects, which are 
    not listed in the 'manage_main' view; to visit them, choose the 'Settings'
    tab. These objects are described in "SilvaServices":SilvaServices.

    The most interesting services are:

    **service_extensions** -- 
    Configuration for Silva core and Extension Products. 
    "SilvaNews":http://www.zope.org/Members/guido_w/SilvaNews objects
    are an example of an extension - they are not part of the Silva
    core and must be installed seperately. Users can create their own 
    extensions (download the 
    "demo zexp":http://www.zope.org/Members/faassen/Silva file for a demo)
    or other custom extensions can be installed and deinstalled. Also the 
    default Silva layout templates can be (re)installed - e.g. after 
    an upgrade - with the |_install_default_layout_| button (existing
    layout templates will not be overwritten, but 'default_' will be 
    prepended to the id).
  
    **service_files** --
    Controls storage of Silva File objects

    **service_members** --
    Controls membership / subscription issues.

    **service_messages** --
    Set up email address for workflow support.

  Silva root <a name="properties">properties</a>
  
    Several key aspects are defined in the properties tab of the Silva
    root.
  
    - **title**: standard Zope title
  
    - **table_width, _cellspacing, _cellpadding, _border**: properties
      which define attributes of (most of) the tables in the SMI 
  
    - **help_url**: defines the URL of the 'Help' link in the
      SMI navigation. This may need adjustment, if
      the id of the Silva root is not 'silva', or if You want to supply
      a customized help page.
  
    - **contact_email, _name**: placeholder properties. In the SMI,
      contact info can be entered in the 'Settings' tab. This information is
      acquired by underlying items.
  
    - **comment**: placeholder. In the SMI, comments can be entered in the
      "Settings Tab":../AuthorEditorChief/MetadataTab. This metadata is 
      **not** acquired by underlying items.

    - **access_restriction**: an experimental feature to restrict
      access to the site to some IP ranges. This is also usually 
      edited via the 'Settings' Tab in the SMI

  Managing users
  
    Managing users via Zope is currently a Manager role issue, and occurs
    in the ZMI, not the SMI. The recommended way of managing users is to
    hook up Zope to LDAP using LDAPUserFolder (see the INSTALL.txt which
    comes with Silva for more information). Alternatively you can manage
    users manually, as described here. 
  
    We recommend creating users in the Silva root (or even above it). This
    locates all users in one place, and provides an overview of all people
    involved. You can assign local roles for users in any place you want
    in Silva. The important point is don't give roles to the users in the
    root folder, but assign roles via the Access tab.
  
    Steps to create an user
  
      - Go to the location where users will be created in the ZMI. (You
        can use the '/manage' link in the breadcrumb trail).

      - If this is the first user to be created, you need to add a special
        Zope object called 'User Folder'. In the "Add" select
        list menu choose "User Folder". This adds a User Folder
        with the id 'acl_users'. One cannot add more than one User Folder.
  
      - Enter the User Folder, and click the |_Add_| button.
  
      - In the upcoming form, choose a name for the user and a password.
        Don't bother with the "Domains" field (unless you're
        using them), and **don't** assign a role. Click |_Add_|.
  
        You (probably) shouldn't assign roles to users in the
        "Roles" select box, because this creates a global role
        for the whole site, overriding settings in the SMI. Note that the
        name can not be changed afterwards.
  
      To modify an user click on the name in the user list.
  
      Delete users by checking the corresponding checkbox to the left of
      the name, and click |_Delete_|.
  
      You will not be asked to confirm your actions. If necessary you can
      use the "Undo" tab to correct errors.

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