[Checkins] SVN: Products.CMFDefault/trunk/docs/narrative/A Converted to ReST

Charlie Clark cvs-admin at zope.org
Tue Apr 3 12:21:02 UTC 2012


Log message for revision 124917:
  Converted to ReST

Changed:
  U   Products.CMFDefault/trunk/docs/narrative/Actor_MembershipManager.rst
  U   Products.CMFDefault/trunk/docs/narrative/Actor_Reviewer.rst
  U   Products.CMFDefault/trunk/docs/narrative/Actor_SiteDesigner.rst
  U   Products.CMFDefault/trunk/docs/narrative/Actor_SiteManager.rst
  U   Products.CMFDefault/trunk/docs/narrative/Actor_SiteVisitor.rst
  U   Products.CMFDefault/trunk/docs/narrative/AddContentFolders.rst

-=-
Modified: Products.CMFDefault/trunk/docs/narrative/Actor_MembershipManager.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/Actor_MembershipManager.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/Actor_MembershipManager.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -1,18 +1,20 @@
 Membership Manager Goals
 ========================
 
-  * Empower many users to collaborate on content production
+Empower many users to collaborate on content production
+-------------------------------------------------------
 
-    - **XXX** "Add a new member to the site using a
-       standard user folder":AddMemberToUserFolder
+- **XXX** :doc:`AddMemberToUserFolder`
 
-  * Delegate responsibilities to site members
+Delegate responsibilities to site members
+-------------------------------------------
 
-    - **XXX** "Change member information and abilities":ChangeMemberInformation
+- **XXX** :doc:`ChangeMemberInformation`
 
-  * Ensure that only appropriate users have access to the site
+Ensure that only appropriate users have access to the site
+------------------------------------------------------------
 
-    - **XXX** "Browse member roster":BrowseMemberRoster
+- **XXX** :doc:`BrowseMemberRoster`
 
-    - **XXX** "Remove a member from the site":RemoveMemberFromSite
+- **XXX** :doc:`RemoveMemberFromSite`
 

Modified: Products.CMFDefault/trunk/docs/narrative/Actor_Reviewer.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/Actor_Reviewer.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/Actor_Reviewer.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -6,15 +6,15 @@
 
 - :doc:`BrowseSubmittedForReview`
 
-  - Brief description of the Action box, with pointers back to
-     where this is set up in the skin.
+  - Brief description of the Action box, with pointers back to where this is
+  set up in the skin.
 
   - Pending lists
 
 - :doc:`ApproveForPublication`
 
-    This should mainly be a pointer back into "Browse content
-    submitted for review and publication"
+  This should mainly be a pointer back into "Browse content submitted for
+  review and publication"
 
 * React quickly to resolve issues with published content.
 

Modified: Products.CMFDefault/trunk/docs/narrative/Actor_SiteDesigner.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/Actor_SiteDesigner.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/Actor_SiteDesigner.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -1,45 +1,45 @@
 Site Designer Goals
 ===================
 
-  * Provide an integrated look and feel for site content.
+Provide an integrated look and feel for site content
+----------------------------------------------------
 
-    - **XXX** "Create new skin for the site":CreateNewSkin
+- **XXX** :doc:`CreateNewSkin`
 
-      o portal_skins Properties tab.  Discussion of Layers and their
-        order of precedence.
+  - portal_skins Properties tab. Discussion of Layers and their order of
+    precedence.
 
-      o Creating a new layer.  Difference between file system layers
-        vs TTW layers.  Don't document actually creating a file system
-        layer, this should likely be a separate use case that
-        refers back to this one.
+  - Creating a new layer. Difference between file system layers vs TTW
+    layers. Don't document actually creating a file system layer, this should
+    likely be a separate use case that refers back to this one.
 
-      o The theory behind customizing methods, but don't refer to
-        specific layers or specific methods/images.
+  - The theory behind customizing methods, but don't refer to specific
+  layers or specific methods/images.
 
-    - **XXX** "Modify skin appearance":ChangeSkinLookAndFeel
+- **XXX** :doc:`ChangeSkinLookAndFeel`
 
-      o Brief description of customizing methods.  Refer back to
-        "Create new skin for the site".
+  - Brief description of customizing methods. Refer back to "Create new
+    skin for the site".
 
-      o Document each layer that deals with appearance with a
-        description of each constituent object (method, image, ...)
+  - Document each layer that deals with appearance with a description of
+    each constituent object (method, image, ...)
 
-  * Give end users an effective way to navigate the site.
+Give end users an effective way to navigate the site
+----------------------------------------------------
 
-    - **XXX** "Change skin behavior":ChangeSkinBehavior
+- **XXX** :doc:`ChangeSkinBehavior`
 
-      o Brief description of customizing methods.  Refer back to
-        "Create new skin for the site description".
+  - Brief description of customizing methods. Refer back to "Create new
+    skin for the site description".
 
-      o Document each layer that deals with behavior with a
-        description of each method.
+  - Document each layer that deals with behavior with a description of each
+    method.
 
-  * Keep the site fresh and interesting for end users.
+Keep the site fresh and interesting for end users
+-------------------------------------------------
 
-    - **XXX** "Change the default skin for the site":ChangeDefaultSiteSkin
+- **XXX** :doc:`ChangeDefaultSiteSkin`
 
-      o Brief description of skins.  Refer back to other skin use
-        cases.
+  o Brief description of skins. Refer back to other skin use cases.
 
-      o portal_skin Properties tab, bottom half.  Very simple form.
-
+  o portal_skin Properties tab, bottom half.  Very simple form.

Modified: Products.CMFDefault/trunk/docs/narrative/Actor_SiteManager.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/Actor_SiteManager.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/Actor_SiteManager.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -1,41 +1,41 @@
 Site Manager Goals
 ==================
 
-  * Provide an online collaboration environment for an organization
-    or community.
+Provide an online collaboration environment for an organization or community
+----------------------------------------------------------------------------
 
-    - "Create a CMF site":CreateCMFSite
+- :doc:`CreateCMFSite`
 
-    - "Configure CMF site":ConfigureCMFSite
+- :doc:`ConfigureCMFSite`
 
-  * Maintain an overall site structure and organization.
+Maintain an overall site structure and organization
+---------------------------------------------------
 
-    - "Create CMF Folder":CreateCMFFolder
+- :doc:`CreateCMFFolder`
 
-    - "Create CMF Topic":CreateCMFTopic
+- :doc:`CreateCMFTopic`
 
-    - **XXX** "Configure CMF Topic":ConfigureCMFTopic
+- **XXX**:doc:`ConfigureCMFTopic`
 
-    - **XXX** "Configure what types of content can be created by
-       members":ConfigureAllowedContentTypes
+- **XXX**:doc:`ConfigureAllowedContentTypes`
 
-  * Implement security policies for the site.
+Implement security policies for the site
+----------------------------------------
 
-    - **XXX** "Configure security for a content object
-       or folder":ConfigureObjectSecurity
+- **XXX**:doc:`ConfigureObjectSecurity`
 
-  * Implement workflow policies for the site.
+Implement workflow policies for the site
+------------------------------------------
 
-    - **XXX** "Associate a workflow with a content
-       type":AssociateWorkflowWithContentType
+- **XXX** :doc:`AssociateWorkflowWithContentType`
 
-  * Implement metadata policies for the site.
+Implement metadata policies for the site
+----------------------------------------
 
-    - **XXX** "Configure required metadata for a content
-       type":ConfigureRequiredMetadata
+- **XXX** :doc:`ConfigureRequiredMetadata`
 
-  * Implement syndication policies for the site.
+Implement syndication policies for the site
+-------------------------------------------
 
-    - **XXX** "Configure what content is released via
-       syndication":ConfigureContentSyndication
+- **XXX** :doc:ConfigureContentSyndication
 

Modified: Products.CMFDefault/trunk/docs/narrative/Actor_SiteVisitor.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/Actor_SiteVisitor.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/Actor_SiteVisitor.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -1,20 +1,21 @@
 Site Vistor Goals
 =================
 
-  * Participate in the community or operations of the site
+Participate in the community or operations of the site
+------------------------------------------------------
 
-    - "Become a member of the site":BecomeAMember
+- :doc:`BecomeAMember`
 
-    - "Log into the site":LoginAsMember
+- "Log into the site":LoginAsMember
 
-    - "Browse community news":BrowseNewsItems
+- "Browse community news":BrowseNewsItems
 
-    - **XXX** "Submit a news item":SubmitNewsItem
+- **XXX** "Submit a news item":SubmitNewsItem
 
-      o Not a stock use case for anonymous visitors;  see
-        "Create Content":CreateNewContent and "Submit
-        Content":SubmitContentForPublication for Content
-        Creator's take.
+  o Not a stock use case for anonymous visitors;  see
+    "Create Content":CreateNewContent and "Submit
+    Content":SubmitContentForPublication for Content
+    Creator's take.
 
   * Quickly find content that is important to him
 

Modified: Products.CMFDefault/trunk/docs/narrative/AddContentFolders.rst
===================================================================
--- Products.CMFDefault/trunk/docs/narrative/AddContentFolders.rst	2012-04-03 10:03:39 UTC (rev 124916)
+++ Products.CMFDefault/trunk/docs/narrative/AddContentFolders.rst	2012-04-03 12:20:58 UTC (rev 124917)
@@ -1,49 +1,55 @@
 Use Case: Add content folders
 =============================
 
-  Actor
+Actor
+-----
 
-    - Content Creator
+Content Creator
 
-  Overview
+Overview
+--------
 
-    As with directories on a filesystem, foldersin a CMF Site allow
-    Content Creators to partition their content into manageable groups.
+As with directories on a filesystem, foldersin a CMF Site allow Content
+Creators to partition their content into manageable groups.
 
-  Assumptions
+Assumptions
+-----------
 
-    - Content Creator has logged into the CMF (see "Login to the
-      Site":LoginAsMember).
+Content Creator has logged into the CMF (see :doc:`LoginAsMember`).
 
-  Procedure
+Procedure
+---------
 
-    1.  Navigate to the folder in which you would like to create sub-folders.
+1. Navigate to the folder in which you would like to create sub-folders.
 
-    2.  In the "Folder contents" view of the folder, select the "New" button.
+2. In the "Folder contents" view of the folder, select the "New" button.
 
-    3.  From the list of addable portal types, select "Folder" by clicking
-        the adjacent radio button.  Supply an ID [1] for the new folder in the
-        input field at the bottom of the page, and click the "Add" button.
+3. From the list of addable portal types, select "Folder" by clicking the
+   adjacent radio button. Supply an ID :ref:`[1]` for the new folder in the input
+   field at the bottom of the page, and click the "Add" button.
 
-    4.  The system will create the new folder using the ID you supplied,
-        and present you with a form for editing the folder's properties.
+4. The system will create the new folder using the ID you supplied, and
+   present you with a form for editing the folder's properties.
 
-    5.  Supply appropriate values as follows:
+5. Supply appropriate values as follows:
 
-        **Title** --  a "human-readable" title for the folder.
+   **Title** --  a "human-readable" title for the folder.
 
-        **Description** -- a brief paragraph summarizing the use to which
-          the folder is put.
+   **Description** -- a brief paragraph summarizing the use to which the
+   folder is put.
 
-    6.  Click the "Change" button.  The system will update the folder's
-        metadata using the values you supply.
+6. Click the "Change" button. The system will update the folder's metadata
+   using the values you supply.
 
-  Notes
+Notes
+-----
 
-  ..[1] Don't confuse the folder's ID with the its Title. ID's cannot
-        contain special characters (e.g., comma, asterisk, brackets,
-        parentheses, etc.)  A good practise is not to use spaces in
-        an ID either. The ID is used in the url to reach the folder's
-        content, so any character which is not allowed in a URI is not
-        allowed in the id (see: "URI RFC",
-        http://www.ietf.org/rfc/rfc2396.txt).
+.. _[1]:
+
+1
+-
+Don't confuse the folder's ID with the its Title. ID's cannot contain special
+characters (e.g., comma, asterisk, brackets, parentheses, etc.) A good
+practise is not to use spaces in an ID either. The ID is used in the url to
+reach the folder's content, so any character which is not allowed in a URI is
+not allowed in the id (see: "URI RFC", http://www.ietf.org/rfc/rfc2396.txt).



More information about the checkins mailing list