<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://weblion.psu.edu/services/documentation/content/RSS">
  <title>Content Management</title>
  <link>http://weblion.psu.edu</link>

  <description>
    
      Documentation and training materials for content managers and content providers. Includes information on managing content using the Plone CMS as well as materials for content strategy and best practices.
    
  </description>

  

  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2011-02-24T19:26:29Z</syn:updateBase>
        

  <image rdf:resource="http://weblion.psu.edu/logo.png"/>

  <items>
    <rdf:Seq>
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/accessibility"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/content-management/short-name"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/content-management/hyperlink-text"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/editing-urls"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/folders"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/twitterfeed"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/information-architecture"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/content-management/links-vs.-content"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/content-management/pdfs"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/links/plone-4-user-manual"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/plone-collections"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/content-types"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/ploneformgen"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/portlet-management"/>
      
      
        <rdf:li rdf:resource="http://weblion.psu.edu/services/documentation/bootcamp-beginners/users-groups-permissions"/>
      
    </rdf:Seq>
  </items>

</channel>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/accessibility">
    <title>Accessibility</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/accessibility</link>
    <description>What You Can Do as a Content Provider</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2>Accessibility and Your Content</h2>
<p>The goal of this document is to give you a quick jump start on knowing what you as a content provider can do to ensure accessibility as defined by the W3C's Web Content Accessibility Guidelines (WCAG).<br /><br />If you want a thorough understanding, go to the excellent <a class="external-link" href="http://webstandards.psu.edu/accessibility">Penn State ITS guide to accessibility</a>.  Where appropriate, this document will simply reference that.<br /><br />If you are really curious -- and ambitious -- read the <a class="external-link" href="http://www.w3.org/WAI/WCAG20/quickref/">quick reference to W3C's Web Content Accessibility Guide</a>. <br /><br />This document is geared toward sites within a content management system and in particular Plone sites.  While there are some Plone-specific notes below, this information applies regardless of the CMS you are using.<br /><br />Many of the page elements are controlled by the templates within your content management system.  If you are a site manager or developer, this document can help you build (or modify, if necessary) your site's templates to adhere to accessibility guidelines.  You should definitely read the ITS guide to accessibility referenced above and in particular, see the Advanced Web Design section of the <a class="external-link" href="http://webstandards.psu.edu/accessibility/checklist">ITS Accessibility Guide checklist</a>.</p>
<p>Following are some of the things you should do.</p>
<h2>Provide text alternatives for any non-text content</h2>
<ol>
<li> <strong>Images</strong> - For images, this means providing alt attributes to your image tags.  Those tags should be descriptive but concise and semantically useful.  In Plone, the title of the image you upload becomes the value of the alt attribute, so create a good title.</li>
<li><strong>Audio and Video </strong>- Alternatives should be offered for pre-recorded video and audio in the form of captions or scripts.  In the case of video, captions are preferred.</li>
<li><strong>Charts and graphs</strong> - Charts and graphs should have either an alt attribute or a longdesc attribute.  Longdesc enables authors to provide a more detailed explanation of the content and can actually point to a file that holds that description.  Also, beware of color coding the chart as that can be inaccessible to a user with color blindness.</li>
<li><strong>Decorative elements</strong> - If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it should be implemented in a way that it can be ignored by assistive technology (e.g. images that have no meaning should have an empty alt tag like this: alt="").</li>
</ol>
<h2>Use Header Tags</h2>
<p>Use header tags (h1 ...h6) to define logical blocks of content.  In Plone, the editor gives users a heading  and one or more subheadings to apply these elements.  In addition to the formatting enhancements, these serve as indicators of information hierarchy within a document.</p>
<h2>Links</h2>
<p>A link should be text that describes the page to which you are linking.  Avoid "Click Here" links.</p>
<p><a class="external-link" href="http://webstandards.psu.edu/accessibility/tech/links">See the PSU accessibility guidelines for a more detailed explanation</a>.</p>
<h2>Using Tables</h2>
<p>Table headers, the scope attribute and the caption tag are necessary to make a table accessible. The summary attribute for simple tables, but can increase the comprehension of more complex tables for people using screen readers.</p>
<p>Table headers help screen readers parse the data in your table.  You should include a scope attribute on the th tags (e.g. &lt;th scope="col"&gt;) to define how the headings relate to the data.</p>
<p>A caption tag within the table element should describe the table contents.</p>
<p>A summary attribute is placed within the table tag and can clarify the organization of the table or provide a quick summary of results.</p>
<p>Marking up a table correctly will most likely require the content provider (or site administrator) to edit the HTML directly.  WYSIWYG editors typically won't address all of these issues.</p>
<p><a class="external-link" href="http://webstandards.psu.edu/accessibility/tech/tables">Examples of good table markup practices</a></p>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Joe Deluca</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-09-25T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/content-management/short-name">
    <title>Appropriate Use of the Short-Name Field</title>
    <link>http://weblion.psu.edu/services/documentation/content-management/short-name</link>
    <description>AgSci's guide to managing Short Names -- and therefore URLs -- on your Plone site</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2011-07-20T16:15:00Z</dc:date>
    <dc:type>Link</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/content-management/hyperlink-text">
    <title>Choosing Appropriate Text For a Hyperlink</title>
    <link>http://weblion.psu.edu/services/documentation/content-management/hyperlink-text</link>
    <description>AgSci's guide to how meaningful link text makes pages more friendly for visitors and search engines. </description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2011-07-20T16:18:05Z</dc:date>
    <dc:type>Link</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/editing-urls">
    <title>Editing URLs</title>
    <link>http://weblion.psu.edu/services/documentation/editing-urls</link>
    <description>How to edit a URL, for instance to make it short and user friendly.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>It's possible to edit the URL (<strong>Short Name</strong>) of any content item on your Plone site. This is useful if you want to make a URL shorter and more readable, or if you want to change it to match a revised <strong>Title</strong>.</p>
<p>No need to worry about breaking links when changing a URL in Plone. The original link still works behind the scenes (this is called an <strong>Alias</strong>, or <strong>Redirect</strong>).</p>
<h2>How to Shorten a URL</h2>
<div>There are a number of ways to do this. Here is the simplest:</div>
<ol>
<li>First, a couple of settings on your site need to be changed. Ask your site administrator or your friendly WebLion representative to enable Short-Name editing for you.  He or she will change settings at the following locations:   
<ul style="list-style-type: square; ">
<li><strong>/@@site-controlpanel</strong></li>
<li><strong>/prefs_user_details</strong> in your user profile.</li>
</ul>
</li>
<li>Once these settings have been changed, you are ready to edit URLs. Log in to your site, go to a content item whose URL you wish to shorten, and <strong>Edit</strong> the item. You should now see an additional field, called <strong>Short Name</strong>. <br /><br /><img alt="Edit Short Name " class="image-inline" src="images/edit-short-name/image_large" /><br /><br />You can now shorten or change the <strong>Short Name</strong> to whatever you wish, as long as it is a well formed URL. Because it's part of the item's web address, the <strong>Short Name</strong> must not contain sp a ces, under_scores, MixedCase, ALLCAPS, or $ym%ols. These can create usability issues or just not work.<br /><br /> <strong>Well Formed Short Names:</strong> 
<ul>
<li>conference</li>
<li> foster-conference</li>
</ul>
<strong>Badly Formed Short Names:</strong> 
<ul>
<li>CONFERENCE</li>
<li>foster conference</li>
<li>FosterConference</li>
<li>foster_conference</li>
<li>foster-conference@psu</li>
</ul>
</li>
<li>Once you have carefully renamed the <strong>Short Name</strong>, save your changes. Your content item will now have a new URL. </li>
</ol>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: beginners</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2012-08-06T18:35:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/folders">
    <title>Folders and Their Contents</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/folders</link>
    <description>Handy Tools for Keeping Track of Your Site's Content</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="training">
<h2>Folders and Information Architecture</h2>
<p><b>Folders</b> and <a class="internal-link" href="07"><b>Collections</b></a> are two of your most important tools for setting up your site's <a class="internal-link" href="../glossary/web-information-architecture">Information Architecture</a> and keeping it under control. Plone provides you with a number of handy tools for managing folders and the items that live in them.</p>
<div><img alt="Simple Site Tree 05: Shows 2nd-Level Items" class="image-inline" src="../images/site-tree-05.png/image_large" /></div>
<h2>Folder Display Options</h2>
<p>Using the <b>Display</b> menu, you can set up a Folder to be viewed in several ways. Experiment with these to see which is the best display option for your Folder's content.</p>
<img alt="Folder Display Options" class="image-inline" src="../images/folder-display-options" />
<h2>Folder Display: Summary View</h2>
<p>The default view for Folders is <b>Folder Summary View</b>. It lists the <b>Title</b> and <b>Description</b> of each item, with a <b>Read More...</b> link leading to the item. When you are logged in, you also see who created the Folder (in this case, <b>by admin</b>), when it was <b>last modified</b>, and can view its <b>History</b>.</p>
<img alt="Folder Display: Summary View" class="image-inline" src="../images/folder-display-summary-view" />
<h2>Folder Display: Summary View on Images Folder</h2>
<p>In a Folder containing images,  <b>Folder Summary View</b> displays an image <b>Thumbnail</b> in addition to the <b>Title</b>, <b>Description</b>, and  link.</p>
<img alt="Folder Display: Summary: Thumbnails" class="image-inline" src="../images/folder-display-summary-images" />
<h2>Folder Display: All Content</h2>
<p>The <b>All Content</b> Folder display shows each item along with its content. This can be handy if, for instance, you have a multi-page set of instructions and you want to give users the option of viewing or printing all the instructions at once.</p>
<img alt="Folder Display: All Content" class="image-inline" src="../images/folder-display-all-content" />
<h2>Folder Display: Tabular View</h2>
<p><b>Tabular View</b> arranges Folder items in a table. As a logged-in user, you see the <b>Author</b> and Date <b>Modified</b> in addition to the <b>Title</b> and Content <b>Type</b>.</p>
<img alt="Folder Display: Tabular" class="image-inline" src="../images/folder-display-tabular" />
<h2>Folder Display: Thumbnail View</h2>
<p><b>Thumbnail View</b> can be used for any Folder, but it is especially useful for Folders containing <b>Images</b>. It's an efficient display of Image <b>Thumbnails</b> with their <b>Titles</b>. Both Thumbnail and Title are linked to the Image Item.</p>
<img alt="Folder Display: Thumbnail" class="image-inline" src="../images/folder-display-thumbnail" />
<h2>Folder Display: Standard View</h2>
<p><b>Standard View</b> shows logged-in users the linked <b>Title</b>, <b>Author</b>, <b>Description</b>, and <b>Modification Date</b> of each Item. Nonlogged-in users see the linked <b>Title</b> and the <b>Description</b>.</p>
<img alt="Folder Display: Standard View" class="image-inline" src="../images/folder-display-standard-view" />
<h2>Folder Display: Select a Content Item as Default View</h2>
<p>It's common to set a Default page<b> </b>for a Folder so that website visitors see this page when they arrive at the Folder—rather than viewing a listing of the Folder's contents. These Default pages are also called Landing pages, or Index pages.<b> </b></p>
<p><b>...Select a content item as default view</b> allows you to select a Page or other Content Item as a Folder's <b>Default View</b>.</p>
<img alt="Folder Display: Default 01" class="image-inline" src="../images/folder-display-default-01" />
<h2>Folder Display: Select Default Item</h2>
<p>Select the <b>Item</b> in the Folder—for instance, a landing Page you have created there—that best serves as the <b>Default View</b>.</p>
<img alt="Folder Display: Default 02" class="image-inline" src="../images/folder-display-default-02" />
<h2>Folder Display: Default View Serves as an Index Page</h2>
<p>When users navigate to this Folder, they will view this Item rather than a listing of the Folder's contents.</p>
<img alt="Folder Display: Default 03" class="image-inline" src="../images/folder-display-default-03" />
<h2>Editing the Default View Vs. Editing the Folder</h2>
<p>One caveat about Folder <b>Default Views</b>: Be careful what you're editing!</p>
<p>Click the <b>Edit</b> tab on a Folder that has a Default View, and you will be greeted with a message warning that you are about to edit the Default View, <i>not</i> the Container. If you want to edit the Folder itself, follow the <b>go here </b>link in this message.</p>
<img alt="Folder Display: Edit Default View" class="image-inline" src="../images/folder-display-edit-default-view" />
<h2>Folder Contents View</h2>
<p>Use a Folder's <b>Contents</b> tab to see <b>Folder's Contents View</b>:</p>
<img alt="Folder Contents Tab" class="image-inline" src="../images/folder-contents-tab/image_large" />
<h2>Folder Contents View: What You Can See</h2>
<p>The <b>Folder Contents View</b> provides a handy list of all the  contents in a Folder:</p>
<img alt="Folder Contents View" class="image-inline" src="../images/folder-contents-view" /><br />
<h2>Folder Contents View: What You Can Do</h2>
<p class="training">Even better, in <b>Folder Contents View</b>, you can perform a number of useful tasks:</p>
<ul>
<li>Click <b>Show all items</b> to see all contents on one screen.</li>
<li>Select a few items. Or <b>Select: All</b>.</li>
<li><b>Reorder</b> items.</li>
<li>Batch handling: <b>Copy</b>, <b>Cut</b>, <b>Rename</b>, <b>Paste</b>, <b>Delete</b>, <b>Change State.</b></li>
<li>Traverse <b>Levels</b>.</li>
</ul>
<h2>Folder Contents View: Show All Items</h2>
<p>If you want to see everything in a Folder that contains many Items, use the numbered tabs or the <b>Show all items</b> link at the bottom of the <b>Folder Contents</b> listing. Another way to see a <b>Folder Contents</b> listing of all Items is to place <b>@@folder_contents?show_all=true</b> after the Folder's URL. For instance:</p>
<p>http://127.0.0.1:8080/chickadees/breeds/@@folder_contents?show_all=true</p>
<img alt="Folder Contents: Show All" class="image-inline" src="../images/folder-contents-show-all" />
<h2>Folder Contents View: Select All</h2>
<p>Use the <b>Select: All</b> link when you need to make changes to all the Items in <b>Folder Contents View</b>.</p>
<img alt="Folder Contents: Select All" class="image-inline" src="../images/folder-contents-select-all" />
<h2>Folder Contents View: Reorder</h2>
<p>You can reorder Items using the slider column along the left side of <b>Folder Contents View</b>. Click next to the Item you want to move, and a slider crossbar will appear. You can now slide the Item up or down in the list.</p>
<img alt="Folder Contents: Reorder Items" class="image-inline" src="../images/folder-contents-reorder" />
<h2>Folder Contents View: Batch Handling</h2>
<p>Check the boxes next to multiple Items that you want to modify. You can now <b>Copy</b>, <b>Cut</b>, <b>Rename</b>, <b>Paste</b>, <b>Delete</b>, or change the  <b>State</b> of these items.</p>
<img alt="Folder Contents: Cut, Copy, Paste..." class="image-inline" src="../images/folder-contents-cut-copy-paste" />
<h2>Folder Contents View: Traverse Levels</h2>
<p>You can also <b>Copy</b>/<b>Cut</b> and <b>Paste</b> Items from Folder to Folder. You can traverse from Folder to Folder staying in <b>Folder Contents View</b> by using the <b>Up one level</b> link.</p>
<img alt="Folder Contents: Traverse Folders" class="image-inline" src="../images/folder-contents-traverse" />
<h2>Folder Contents View: Rename</h2>
<img alt="Folder Contents: Rename 01" class="image-inline" src="../images/folder-contents-rename-01" />
<h2>Folder Contents View: Rename</h2>
<img alt="Folder Contents: Rename 02" class="image-inline" src="../images/folder-contents-rename-02" />
<h2>Folder Contents View: Rename</h2>
<img alt="Folder Contents: Rename 03" class="image-inline" src="../images/folder-contents-rename-03" />
<h2>Folder Contents View: Change State</h2>
<img alt="Folder Contents: Change State 01" class="image-inline" src="../images/folder-contents-change-state-01" />
<h2>Folder Contents View: Change State</h2>
<img alt="Folder Contents: Change State 02" class="image-inline" src="../images/folder-contents-change-state-02" />
<h2>Folder Contents View: Change State</h2>
<img alt="Folder Contents: Change State 03" class="image-inline" src="../images/folder-contents-change-state-03" /><br />
<h2>Restricting Content Types in a Folder</h2>
<p>By default, you can add any Content Type to a Folder. Restricting this is a simple and effective way to control <i>what</i> content gets created <i>where</i> on your site.</p>
<p>To do this, select the <b>Restrictions</b> choice in the Add new... menu:</p>
<img alt="Restrict what content types get added to a folder." class="image-inline" src="../images/restrictions" />
<h2>Choose The Types You Want to Restrict</h2>
<p>To choose the types you want to restrict from your folder, select <b>Specify types manually</b>, and then unselect the types you want to restrict.</p>
<p>You also have the option to allow certain types to be added under a <b>More...</b> submenu.</p>
<img alt="Restrict what content types can be added to a folder." class="image-inline" src="../images/restrictions-02" />
<h2>Restriction Simplifies, Adds Control</h2>
<p>In addition to providing more control, restricting items that can be added to a folder simplifies the interface and can help prevent content-provider confusion.</p>
<img alt="Folder with Items Restricted" class="image-inline" src="../images/restrictions-03" />
<h5 align="right"><a class="internal-link" href="plone-collections/presentation_view" title="Tags and Collection">next...</a></h5>
</div>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-04-21T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/twitterfeed">
    <title>How to Add a Twitter Feed on Your Plone Site</title>
    <link>http://weblion.psu.edu/services/documentation/twitterfeed</link>
    <description>How you can grab a Twitter RSS feed and place it in a Plone RSS portlet.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<ol>
<li>First you have to grab an RSS feed off the Twitter site. Twitter no longer posts a link to RSS feeds, but you can do this trick: Go to the following URL, but replace <strong>xxxxx</strong> with the TwitterFeed username:<br /><br />http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=<strong>xxxxx</strong><br /><br />For example:<br /><br /><a class="external-link" href="http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=weblion">http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=weblion<br /></a><span><br /> </span></li>
<li>When you do this, you should see the content of the Twitter RSS feed. Copy this URL; you will need it in a minute.</li>
<li> Click <strong>Manage Portlets</strong> the Folder or Page where you want the Twitter feed to display. </li>
<li>In the Add Portlet menu, select <strong>RSS Feed</strong>.<br /><br /><img alt="Select RSS Feed in Add Portlets Menu" class="image-inline" src="images/rss-feed-02/" /><br /><br /></li>
<li>You will see the following screen:<br /><br /><img alt="RSS Portlet" class="image-inline" src="images/rss-portlet/" /><br /><br />In the <strong>Number of items to display</strong> field, Indicate how many Twitter posts you want to display in the portlet. You can edit the portlet and change this number any time.<br /><br />In the URL of RSS feed field, place the URL you created in Step 1. For example, <br /><br /> <a class="external-link" href="http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=weblion">http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=weblion</a><br /><br />The <strong>Feed reload timeout</strong> field indicates the number of minutes that will pass between times when the portlet will refresh data on your site. The default is 100 minutes. That means that every 100 minutes, the portlet will refresh itself and show any new Tweets posted during that time. If needed, you can shorten the <strong>Feed reload timeout </strong>so that it posts new Tweets more often.<br /><br /></li>
<li><strong>Save</strong> your changes.<br /><br /></li>
<li>Follow the <strong>Return</strong> link to go back to your Page or Folder.<br /><br /></li>
<li>That's it! Your RSS feed should now be displaying.</li>
</ol>
<p><strong>Why is my RSS portlet title so weird? Can I change it?</strong><br />If you're asking this question, you're probably still using Plone 3. In Plone 3, it is not possible to change the Title of RSS portlets -- the portlet grabs the title from part of the feed. In Plone 4, you will be able to specify a Title of your choice for RSS feeds.</p>
<div></div>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: beginners</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2012-08-06T18:20:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/information-architecture">
    <title>Information Architecture</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/information-architecture</link>
    <description>An Introduction to Your Site's Information Architecture</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2>Getting Started</h2>
<div class="training">
<ul>
<li>Organize content in a logical structure so that users can easily find what they're looking for. </li>
<li>Plan to invest some time organizing your site. </li>
<li>Visitors approach your content from many different perspectives. </li>
<li>Helping visitors find what they need also helps contributors find where to share their knowledge. </li>
<li>User needs may also change over time, making it important that you plan to maintain your site's organization over time.</li>
</ul>
<ul>
</ul>
<h2>Anatomy of a Simple Plone Site</h2>
<p>What you see here is a map of a simple Plone site. Here's what's important about its structure...</p>
<img alt="Anatomy of Information Architecture" class="image-inline" height="305" src="images/ia-anatomy.png/image_large" width="546" /> 
<ul>
<p>At the top of this structure is the <b>Home Page</b>. The Home Page stands alone at the <b>root</b> of the site—that is, it does <i><b>not</b></i> live inside a <b>Folder</b>.</p>
<p>Next, we have three <b>Folders</b>, the titles of which represent the site's main subtopics.</p>
<p>The content of each <b>Page</b> within a Folder is a further breakdown of that main subtopic.</p>
<p>With the exception of the Home Page, <i><b>all</b></i> Pages  and other files on this site are organized within their proper <b>Folders</b>.</p>
</ul>
<ul>
<li>This is the goal: <b>A place for everything, and everything in its place</b>. </li>
</ul>
</div>
<div class="training" style="padding-left: 30px; "></div>
<p class="training" style="padding-left: 30px; ">Organizing content in a logical hierarchy and storing files and  content  types in their proper places is an important part of what is  called  sound web <a class="internal-link" href="../glossary/web-information-architecture" title="Web Information Architecture"><b>Information Architecture</b></a>.</p>
<div class="training">
<h2>Levels of a Simple Plone Site</h2>
<img alt="Level 1 Information Architecture" class="image-inline" height="311" src="images/ia-level1.png/image_large" width="557" /> 
<ul>
</ul>
<ul>
<li>The Home Page and top Folders are at <b>Level 1</b>, or the <b>root</b> of the site.</li>
</ul>
<h2>Levels of a Simple Plone Site</h2>
<img alt="Level 2 Information Architecture" class="image-inline" height="311" src="images/ia-level2.png/image_large" width="562" /> 
<ul>
</ul>
<ul>
<li>The <b>Pages</b> within the top Folders on this site are at <b>Level 2</b>.</li>
</ul>
<p>This site has only 2 levels.  Adding more Folders inside of Folders  will make the site deeper and more complex.  But as you continue deeper  down the trail of breadcrumbs, ask yourself, "Do my users need this  extra level?"  Or is there a better way to organize this information?</p>
<h2>Best Practices for Setting Up a Structure</h2>
<ul>
<li>Inventory content.</li>
<p>Conduct an inventory of manageable pieces of sample content.  Often, breaking down a single section of content will help you navigate an otherwise vast sea of information.</p>
<li>Look for organizing principles.</li>
<p>Take some time to discover common threads, recurring themes, and organizing principles within your site's content.</p>
<li>Perform card sort.</li>
<p><a class="external-link" href="http://en.wikipedia.org/wiki/Card_sorting">Card sorting</a> is a common exercise that involves putting important subjects on cards, and then organizing the cards into groups.  Should any cards appear in more than one group?  Are there relationships between some of the groups?</p>
<li>Look for content types.</li>
<p>Do any of the groups match <a class="internal-link" href="content-types/presentation_view" title="Plone's Content Types">Plone Content Types?</a></p>
</ul>
<ul>
<li>Look for hierarchies, such as outlines, trees, maps.  Examples: steps in a process, events in time, places, or disciplines.. Create <b>folder structures</b>.</li>
<p>If some of the groups form a hierarchy, such as an outline of topics and subtopics, a tree of branches and leaves, or a map of areas within areas, create a structure of folders for those groups.  You may discover groups covering steps in a process, events in time, places, or disciplines, for example.</p>
<li>Look for groups of ownership.  Create <b>folders</b>.</li>
<p>If some of the groups follow ownership of the content within them (such as the organization chart), create folders for those groups.</p>
<li>Look for other cards &amp; groups that don't fit into a single hierarchy.  Create <b>tags &amp; collections</b>.</li>
<p>Do you have groups left over, or cards that fit into multiple groups?  For example, you have created a set of folders for steps in a process, but have left over groups for different audiences who all use that process.  Create tags on your content items to represent those audiences.  Use Plone Collections to display the content tagged as relevant to each audience.</p>
</ul>
<h2>Content Growth</h2>
<p>A common request that content managers get is to "put up a webpage."  Frequently what this really means is not a single Page but a whole new  section somewhere on the website. When it's time to put up this new  information, assess the current amount of content and its potential for  expanding.</p>
<ul>
<li> Could this site section grow to be more than one <b>Page</b>? Is it already too much for one <b>Page</b>? </li>
<li>If yes, then create a <b>Folder</b>.</li>
</ul>
<ul>
</ul>
<h2>Associated Content</h2>
<p>When creating new content you should always ask yourself:</p>
<ul>
<li>How does my new content fit with that existing content? </li>
<li>Should it live parallel to that content? </li>
<li>Should it be a subset? </li>
<li>What makes the most sense to users? </li>
<li>Is this new content <b>duplicating</b> existing content?</li>
</ul>
<ul>
</ul>
</div>
<h2>Periodic Review</h2>
<p>Conducting a periodic review of your IA is highly recommended.  Ask yourself these questions:</p>
<ul>
<li>Who does your organization <i><b>want</b></i> to find with this content and why? </li>
<li>Who among your site's audiences actually <b><i>need</i></b> this content and why? </li>
<li>Do your  site analytics show that users are searching for this subject matter?</li>
</ul>
<ul>
</ul>
<p>However, as content is added and subtracted, the scope of the information you are providing may begin to change, even at the highest levels of the site.  An example top-level folder shift example: chickadees (start) -&gt; chickadee  habits (after 3 months) -&gt; male chickadee habits (after 6 months).</p>
<p>Your audience may change as well.  Perhaps initially your organization sought to appeal to developers in an effort to bring more talent and skills to the community.  After building some marketable success stories, your organization next wants to target administrative decision-makers for buy-in.</p>
<p>Remember, that the world around you is constantly changing, and your IA should be positioned to adapt.</p>
<h5 align="right"><a class="internal-link" href="accessibility/presentation_view" title="Accessibility">next...</a></h5>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-08-13T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/content-management/links-vs.-content">
    <title>Links Vs. Content</title>
    <link>http://weblion.psu.edu/services/documentation/content-management/links-vs.-content</link>
    <description>Don't be a Link Farmer! AgSci's guide to why you should avoid maintaining large collections of links on your site.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2011-07-20T16:13:31Z</dc:date>
    <dc:type>Link</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/content-management/pdfs">
    <title>PDF - Appropriate Uses</title>
    <link>http://weblion.psu.edu/services/documentation/content-management/pdfs</link>
    <description>When is it appropriate to use a PDF? When should a page be used instead? This is AgSci's guide on judicious use of PDFs on the Web.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2011-07-20T15:11:47Z</dc:date>
    <dc:type>Link</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/links/plone-4-user-manual">
    <title>Plone 4 User Manual</title>
    <link>http://weblion.psu.edu/services/documentation/links/plone-4-user-manual</link>
    <description>A Guide for Plone Content Creators and Managers</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: beginners</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2011-02-24T21:15:00Z</dc:date>
    <dc:type>Link</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/plone-collections">
    <title>Plone Collections</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/plone-collections</link>
    <description>Dynamically Sort and Display Your Content</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2>What Is a Collection?</h2>
<h3>It's a container that dynamically sorts and displays content based on a set of criteria regardless of where that content may be stored on your site.</h3>
<h3>Similar to:</h3>
<ul>
<li>Search engine returning results</li>
<li>Query from a database</li>
<li>Itunes Playlists</li>
</ul>
<h2>Itunes Example: Joe Satriani smart playlist. ﻿</h2>
<h3><img alt="Satriani itunes rule" class="image-inline" src="../images/satriani-itunes-rule" /></h3>
<p>Each time I put in a new cd or add new music by Joe a army of trained monkeys goes and puts the songs inside of my playlist.</p>
<h2>Trained Monkeys</h2>
<h3><img alt="monkey salute" class="image-inline" src="../images/monkey-salute" /></h3>
<h2>Search Result</h2>
<h3><img alt="Satriani Playlist" class="image-inline" src="../images/satriani-playlist" /></h3>
<h2>But Joe is also in multiple bands.</h2>
<p>I want this music to be included in my Satriani's playlist so I change the search query so that it matches any of the rules.</p>
<ul>
<li>Get any song that has Joe Satraini as a artist OR</li>
<li>Grab any song that Chickenfoot is the artist as well. </li>
</ul>
<h2>Modified Search Rule</h2>
<h3><img alt="Satriani chickenfoot rule" class="image-inline" src="../images/satriani-chickenfoot-rule" /></h3>
<h2>Result:</h2>
<h3><img alt="Chicken Satch Collection" class="image-inline" src="../images/chicken-satch-collection" /></h3>
<h2>Many attributes</h2>
<p>There are many kinds of attributes I can search for:</p>
<ul>
<li>Artist</li>
<li>Album rating</li>
<li>album artwork</li>
<li>composer</li>
<li>description</li>
<li>album artist</li>
<li>date added</li>
<li>date modified</li>
<li>......</li>
</ul>
<p> </p>
<h2>Attributes</h2>
<h3><img alt="Satriani attributes" class="image-inline" src="../images/satriani-attributes" /></h3>
<h2>Song limits</h2>
<p>I can limit how many songs this playlist can get. I can have it get the last 10 songs that was added to the playlist.</p>
<h3><img alt="Satriani limit amount of songs" class="image-inline" src="../images/satriani-limit-amount-of-songs" /></h3>
<p>This is how collections works in plone. It is a playlist of news stories, events, latest photos...</p>
<h2>Collections are Powerful!</h2>
<h3><img alt="Strong man" class="image-inline" src="../images/strongman.jpg" /></h3>
<h2>They Reduce Redundancy!</h2>
<h3><img alt="They Reduce Redundancy" class="image-inline" src="../images/redundancy.png" /></h3>
<h2>They Reduce Redundancy!</h2>
<ul>
<li>Oh, and outdated content</li>
<li>Broken links, too!</li>
</ul>
<h2>Harness the Power!</h2>
<h3>Here are just a few great options:</h3>
<ul>
<li>Categories</li>
<li>Date of publication</li>
<li>Type of content</li>
</ul>
<p>Collections reduce the redundant content, outdated content, and unintentionally broken links.</p>
<h3>Common Applications for Collections</h3>
<ul>
<li>News</li>
<li>Events</li>
<li>Photos displayed by date range</li>
<li>Content displayed by category</li>
</ul>
<h2>Collection Demo</h2>
<p>Excuse me while I switch Machines...</p>
<h2>Other Search Terms that are useful...</h2>
<p> </p>
<h2>Dates</h2>
<h3><img alt="Myriad Dates" class="image-inline" src="../images/myriaddates.jpg" /></h3>
<h3>There are a LOT of Dates!</h3>
<p>Date results display the results with the oldest date first, otherwise known as ascending order</p>
<ul>
<li>Creation Date - the date the document was made. You can't change the creation date of an object.</li>
<li>Effective Date - the date when an object is published. You can change the effective date.</li>
<li>Expiration Date - refers to the day that the item will no longer be   publicly available.</li>
<li>Modification Date- the date the object was last edited. You can't customize this date.</li>
<li>Event Specific Dates - <i>only</i> apply to objects that are <b>Events.</b></li>
<li>Start Date - the date that an event starts</li>
<li>End Date - the date that the event ends </li>
</ul>
<p><b>Creation Date</b> and <b>Effective Date</b> are  very similar. They both represent a beginning point of an object. Keep  in mind when   choosing which one you want to use, an object can be  created long before   it's published. Thus you would get different  results in a Collection   depending on which date you used.</p>
<p>We recommend using <b>Effective Date</b> rather than Creation Date    for date-oriented collections. This way, your collection shows results    based on when they became viewable to the public, which is usually more    relevant to the audience of your collection. Also, you can manually    adjust the Effective Date to control the sort order, which you can't do    with Creation Date.</p>
<p>The <b>Expiration Date</b> is also customizable through the Edit    tab. By default,  objects have no expiration date.</p>
<p>The <b>Modification Date</b> is the date the object was last edited.  Note   that this date is determined the day the object is created and  will   automatically change every time the object is edited. There is no  way to   customize this date.</p>
<p><b>Event specific dates</b> -<b> </b><b>Start and End Dates</b> are  very effective for creating recent events and upcoming events  collections that will let your audience know what your   organization is  doing and will be doing in the future.</p>
<h2>Setting Dates</h2>
<p>Setting up Criteria for dates can be confusing.   They have a setup  that is not like any of the other Criteria. First,   you have to choose  whether you want a Relative Date or a Date Range.</p>
<h3><img alt="Date Criteria Types" class="image-inline" src="../images/datecriteriatype.png" /></h3>
<p>A <b>Date Range</b> will allow you to <b>specify an exact range of dates</b>,     such as 01/02/08 to 02/02/08. The Date Range is useful when you want    to  create a Collection with a static date that won't change.The <b>Relative Date</b> allows you to construct a <b>conditional statement</b>.  For instance, items modified less than 5 days in the past.  The   Relative  Date can be very useful as it will allow you to create    Collections that  are automatically updating themselves, such as a    Recent News collection  or an Upcoming Event section.</p>
<h2>Date Range</h2>
<p>The <b>Date Range</b> is very easy to understand. Both a Start Date     and End Date are required (do not confuse these terms with the Event     Specific dates!). The Date Range allows us to enter a beginning and an     end date and the display everything within that time frame. Notice   also   that it allows us to specify a specific time of day as well.</p>
<h3><img alt="Date Range Criterion" class="image-inline" src="../images/daterangecriterion.png" /></h3>
<h2>Relative Date</h2>
<p>Looking first at the Relative Date option, you can see we have three options to fill out.</p>
<h3><img alt="Relative Date Criterion" class="image-inline" src="../images/relativedatecriterion.png" /></h3>
<h3>I want the results to include objects <b>More or Less</b> than <b>Which Day</b>, <b>In the Past or Future</b>.</h3>
<p>The first option is <b>Which Day</b>. This allows us to select the number of days our criterion will include. One of the options is called <i>Now</i>. Using this will set the date range to the current day. The other two options do not matter and can be ignored when using <i>Now</i>.</p>
<p>If you are choosing one of the other two options, here is a statement    you'll want to learn: I want the results to include objects <b>More or Less</b> than <b>Which Day</b>, <b>In the Past or Future</b>.</p>
<p>Keeping that in mind, the second option is <b>In the Past or Future</b>. This enables us to choose whether we are looking forward or backward into time.</p>
<p>The last option is <b>More or Less</b>. Here we can choose from three options. <i>Less than</i> allows us to include everything from now to a period of time equal to or less than the <b>Which Day </b>setting, either in the past or future. <i>More than</i> will include everything from beyond our specified number of days equal to or more than <b>Which Day</b>. Finally <i>On the Day </i>will only include things that are on the day we specified in the <b>Which Day</b>. Using the example in the image above if we had selected <i>On the Day</i> instead of <i>Less than</i> our Collection would display only objects that were modified (we are using the Modification Date criterion) 5 days ago.</p>
<p>Now, try reading the statement from above, substituting in the field options you chose.</p>
<h2>Creator</h2>
<p>When using the Creator criterion, we are filtering objects based on  who created them. This might be useful if you want to do a featured  author section, where  you would only want to display content on your  site that has been  created by a certain author.</p>
<p>As you can see we have several options for our criteria type. They   allow us to restrict the creator to the person currently logged in,   enter the name of another user as text, or to select users from a list.</p>
<h3><img alt="Creator" class="image-inline" src="../images/creator.png" /></h3>
<p>If you want to display results from multiple users, you would need to use the <b>List of values</b> option. Otherwise you would normally use the <b>Text</b> option unless the  creator you wanted to select was yourself in which case you would use  <b>Restrict to current user</b>.</p>
<h2>Description</h2>
<p>The Description field is essentially a search box type criterion.  However, instead of searching the title and body of a page, it will only  search for the text in the Description field of a content object. This  criterion is only really useful if you fill  out the Description field  consistently for all your content objects.</p>
<h3><img alt="Description" class="image-inline" src="../images/description.png" /></h3>
<h2>Location</h2>
<p>Using the Location criterion is much like specifying a location when   you search for a document on your hard drive. By specifying a Location   criterion, the results that are displayed in your Collection will only  come from that location,  most commonly, a folder. This can be useful if  you only want to display  content that is in the About Us section of  your site, for example. This  is also useful for narrowing Collection  results when combined with other  criteria.</p>
<h3><img alt="Location" class="image-inline" src="../images/copy_of_location.png" /></h3>
<h2>Specify a Location</h2>
<p>To specify a Location, simply click the Add button,  which will pop up a new window showing you a directory of your site.</p>
<h3><img alt="Add Location" class="image-inline" src="../images/addlocation.png" /></h3>
<p>Put a check next to the item you want.</p>
<p>You can open folders to view content contained within them by   clicking directly on the title of the folder you  want to open. You may  also use the Search box to search for the Title of  an object.</p>
<h2>Search Text</h2>
<p>Search Text is a very useful criterion. It is similar to the  search  box on your site or an Internet search engine. It takes the text  you  specify and searches the Title, Description, and Body of all objects   and returns any that have the word or phrase you specify.  This is  useful when you want to find objects that have to deal with a  certain  thing, especially if the word or phrase appears across many  content  types.</p>
<p><img alt="Search Text" class="image-inline" src="../images/searchtext.png" /></p>
<h2>Related To, Part 1</h2>
<p>The Related To field is another field, like Category, that <b>must be specified on a content object prior to being used for a Collection</b>.   The Related Items field on an object (found in the Edit area, inside  the Categories tab) lets you specify which other objects  in your site  are similar or are relevant to the object you created. By  specifying  this field, when you create an object you can create a web of  related  content that will reference each other (think of a "see also"  kind of  function).</p>
<h3><img alt="Related Items" class="image-inline" src="../images/relateditems.png" /></h3>
<p>When you have done this, you can use the Related To  criterion in a  Collection to display anything related to a specific  object.</p>
<h2>Related To, Part 2</h2>
<ul>
<li> Remember the Related To Values list does not work based on   which  objects are related to content, but on which objects have another    object related to it.</li>
</ul>
<h3></h3>
<h3><img alt="Related Items" class="image-inline" src="../images/relateditemcriteria.png" /></h3>
<h2>Setting Sort Order</h2>
<h3><img alt="Chickadee Criteria" class="image-inline" src="../images/chickadeecriteria.png" /></h3>
<p><b>Set Sort Order</b> allows a field to sort the results of a  collection. Checking Reverse causes the results to display in reverse of  the default display order.</p>
<p>After saving the collection, the search criteria  will be applied and the  results displayed when the collection is  viewed.  You can create any  number of collections for such custom  views.</p>
<p>Also, understand that you must <b>publish</b> the collection for results to be visible to the anonymous user.</p>
<h2>Setting the Sort Order,  Option One:</h2>
<p>The order that search results are displayed in a collection is determined by <b>Sort Order</b>.</p>
<ul>
<li>Text results - Results display in alphabetical order</li>
<li>Creator</li>
<li>Short name - in Plone speak, another name for the URL of an object</li>
<li>Title</li>
</ul>
<h2>Setting the Sort Order, Option Two:</h2>
<ul>
<li>Object property results - objects are grouped together by the specified properties</li>
<ul>
<li>Tags</li>
<li>Item type</li>
<li>Related to - limits results to only those objects that have Related To information specified on their properties</li>
<li>State</li>
</ul>
</ul>
<h2>Setting the Sort Order, Option Three:</h2>
<ul>
<li>Date results - displays the results with the oldest date first, otherwise known as ascending order</li>
<li>Creation Date - the date the document was made. You can't change the creation date of   an object.</li>
<li>Effective Date - the date when an object is published</li>
<li>Expiration Date - refers to the day that the item will no longer be   publicly available</li>
<li>Modification Date- the date the object was last edited</li>
<li>Event Specific Dates - <i>only</i> apply to objects that are <b>Events</b></li>
<li>Start Date - the date that an event starts</li>
<li>End Date - the date that the event ends</li>
</ul>
<h2>Ready to See Your Collection?</h2>
<p>Just click View!</p>
<h3><img alt="View your collection" class="image-inline" src="../images/viewcollection.png" />.</h3>
<h5 align="right"><a class="internal-link" href="portlet-management/presentation_view" title="Managing Content in Plone, Part VIII">next...</a></h5>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Beth Phillips</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: beginners</dc:subject>
    
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    
      <dc:subject>documentation: training</dc:subject>
    
    <dc:date>2010-05-29T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/content-types">
    <title>Plone's Content Types</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/content-types</link>
    <description>And How to Add and Edit Them</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="training">
<h2>Common Content Types</h2>
<p>Plone comes with several different <strong>Content Types</strong>. In addition, your web admin may have created some new ones. Or, the admin may have installed a product such as <a class="external-link" href="http://plone.org/products/faculty-staff-directory">Faculty Staff Directory</a>, which includes Content Types such as <strong>Person</strong>.</p>
<p>Having a good understanding of different Content Types, their purposes, and where best to place them on your site will help you to keep your web presence well <i><strong>architectured</strong></i>—that is, organized to best meet the needs of your users. <i><a class="external-link" href="http://www.webmonkey.com/2010/02/information_architecture_tutorial/">If you'd like to learn more about web </a></i><a class="external-link" href="http://www.webmonkey.com/2010/02/information_architecture_tutorial/"><i> </i></a><i><a class="external-link" href="http://www.webmonkey.com/2010/02/information_architecture_tutorial/">information architecture,</a></i><i><a class="external-link" href="http://www.webmonkey.com/2010/02/information_architecture_tutorial/"> WebMonkey has a good introductory tutorial...</a></i></p>
<p><strong>Here are the Plone Content Types you will use most often:</strong></p>
<ul>
<li>Event</li>
<li>News Item</li>
<li>Page</li>
<li>Image</li>
<li>File</li>
<li>Link</li>
</ul>
<h2>Containers</h2>
<p>Some of Plone's content types—see the two listed below—serve as containers for other content types. These are sometimes referred to as <i><strong>folderish </strong></i>or<i><strong> containerish</strong></i> Content Types. More about these later.</p>
<p><strong>Folderish Content Types (Containers):</strong></p>
<ul>
<li>Folder</li>
<li>Collection</li>
</ul>
<h2>Logged-in Versus Anonymous View</h2>
<p>Before we go into detail about each content type, you should know that what you see while you are adding and editing content is somewhat different from what anonymous users—the public—sees. It's a good idea to keep both a logged-in and an anonymous view open so that you can check back and forth. Depending on how your site is set up, here are a couple of ways you can do this:</p>
<ul>
<li>Open two different <strong>browsers</strong>. Stay logged out of one.</li>
<li>If your site uses <strong>https</strong>, open a different browser <strong>tab</strong>. Remove the <strong>s</strong> from <strong>https</strong> in the second tab.</li>
</ul>
<h2>Event</h2>
<p>The <strong>Event</strong> Content Type—not surprisingly—is specifically used for managing information about upcoming events. It allows you to post events without worrying about removing the information from your site once the event is over.</p>
<p>The <strong>Event</strong> Content Type also includes a function that allows your users to add your posted events to their own calendars, using iCal or vCal.</p>
<p><strong>The Event Content Type is...</strong></p>
<ul>
<li>Used for <i><strong>upcoming</strong></i> events</li>
<li>Think of these as <strong>calendar</strong> items</li>
</ul>
<h2>Event: Event Folder(s)</h2>
<p>In theory, you could add an event anywhere on your site. However, your site administrator most likely has provided a specific folder (or folders) for adding events. Plone sites have an Events Folder by default.</p>
<div><img alt="Site Tree: Events" class="image-inline" src="../images/site-tree-events.png/image_large" /></div>
<h2>Event: Adding an Event</h2>
<p>In your site's event folder(s), click <strong>Add Event</strong>.</p>
<div><img alt="Add An Event" class="image-inline" src="../images/add-event.png/image_large" /></div>
<h2>Event: Title and Description</h2>
<p>Provide a <a class="internal-link" href="../glossary/web-page-title" title="Web Page Title"><strong>Title</strong></a> and <strong>Description</strong> for your event that is clear (and inviting) to your readers. The Title and Description also can <a class="internal-link" href="../glossary/search-engine-friendly" title="Search-Engine Friendly">draw in readers using search engines</a>.</p>
<div><img alt="Event: Title and Description" class="image-inline" src="../images/events-title-description.png/image_large" /></div>
<h2>Event: Location and Dates</h2>
<p>Add the event's <strong>Location</strong>. Be as specific as you need to be.</p>
<p>Add the <strong>Start</strong> and <strong>End</strong> dates and times. Your event will no longer appear in your site's listing of upcoming events once the <strong>End</strong> date and time have passed—you don't need to remember to unpost it.</p>
<div><img alt="Event: Location, Dates, Body Text" class="image-inline" src="../images/event-location.png/image_large" /></div>
<h2>Event: Attendees</h2>
<p>Who should attend your event? Who might be interested? Is it for a certain group only? You can provide this information under <strong>Attendees</strong>.</p>
<div><img alt="Event: Attendees" class="image-inline" src="../images/events-attendees.png/image_large" /></div>
<h2>Event: URL and Contact Info</h2>
<p>Is there a website with further information about the event that readers could use? Add this under <strong>Event URL</strong>. Be sure to include the <strong>http://</strong> part of the web address.</p>
<p>You can also add the <strong>Name</strong>, <strong>E-mail</strong>, and <strong>Phone</strong> of whom to contact for more information.</p>
<div><img alt="Event: Contact Info" class="image-inline" src="../images/event-contact.png/image_large" /></div>
<h2>Event: Save</h2>
<p>Be sure to <strong>Save</strong> your work!</p>
<div><img alt="Event: Save" class="image-inline" src="../images/event-save.png/image_large" /></div>
<h2>Event: Publishing</h2>
<p>Your Event will not be viewable by the public until you <strong>Publish</strong> it. To do this, change <strong>Private</strong> to <strong>Publish</strong> under the <strong>State</strong> menu.</p>
<div><img alt="Event: Publish" class="image-inline" src="../images/event-publish.png/image_large" /></div>
<h2>Event: Published View</h2>
<p>Your Event is now published! This is essentially what the information will look like to the public (though your site administrator may have made some styling changes):</p>
<div><img alt="Event: Public View" class="image-inline" src="../images/event-publicview.png/image_large" /></div>
<h2>Event: Edit</h2>
<p>To make further changes to your Event, click <strong>Edit</strong>.</p>
<div><img alt="Event: Edit" class="image-inline" src="../images/event-edit.png/image_large" /></div>
<h2>Event: Categorization</h2>
<p>Your site administrator may have set up some <strong>Categories</strong> (also known as tags) under <strong>Event Type(s)</strong> so that you can choose the appropriate one(s).</p>
<div><img alt="Event: Categorization" class="image-inline" src="../images/events-categories.png/image_large" /></div>
<h2>Event: The Importance of Categories (aka Tags)</h2>
<p>These Categories can be  very important. Depending on what your site administrator has set up, Categories can influence where your Event appears  on the website, whether it shows up on the home page, and that sort of  thing.</p>
<div><img alt="this image is used on the training page at http://weblion.psu.edu/services/documentation/bootcamp-beginners/content-types." class="image-inline" src="../images/events-categorization-4.3/image_large" /></div>
<h2>Event: Publishing Date</h2>
<p>There is another set of <strong>Dates</strong> controls that may prove useful for your Event posting. This Dates link is in the bar of links under <strong>Edit Event</strong>, next to Categorization.</p>
<div><img alt="Event: Publish Date 01" class="image-inline" src="../images/events-publish-date.png/image_large" /></div>
<h2>Event: Publishing Date</h2>
<div><img alt="Event: Publishing Date 02" class="image-inline" src="../images/events-publishing-date-02.png/image_large" /></div>
<p>You can specify a <strong>Publishing Date and Time</strong> when you would like  an Event to be viewable by the public on your site. This is handy  because it can allow you to place Event information on your site far  ahead of time and set it to publish itself closer to the time of the  Event—one less thing for you to remember to do.</p>
<p>Note that there is also an <strong>Expiration Date</strong>. When working with  Events, most of the time you should leave this blank. An Event removes  itself from your site's Events listings once the Event's date and time  has passed anyway.</p>
<p>As you will see, the <strong>Expiration Date</strong> can be very useful for other content types, though.</p>
<h2>News Item</h2>
<p><strong>News Items</strong> are used to post the following kind of information:</p>
<ul>
<li>News Stories, Press Releases</li>
<li>Announcements: New Hires, Awards...</li>
<li>Wrapups, Results of Past Events</li>
<li>Newsletter Articles</li>
<li>Job Postings</li>
</ul>
<h2>News Item: News Folder</h2>
<p>In theory, you could add <strong>News Items</strong> anywhere on your site. But chances are, your site administrator has provided a specified <strong>News Folder</strong> (Plone sites actually have one by default). Some sites have News Folders in different site sections.</p>
<div><img alt="Site Tree: News" class="image-inline" src="../images/site-tree-news.png/image_large" /></div>
<h2>News Item: Adding a News Item</h2>
<p>You add a <strong>News Item</strong> in the same way that you add an Event. Go to the News Folder, and select News Item under the <strong>Add new...</strong> menu.</p>
<div><img alt="News: Add" class="image-inline" src="../images/news-add.png/image_large" /></div>
<h2>News Item: Title, Description, Body Text</h2>
<p>Provide a <a class="internal-link" href="../glossary/web-page-title" title="Web Page Title"><strong>Title</strong></a> and a <strong>Summary</strong> that is informative and inviting for your users and that is <a class="internal-link" href="../glossary/search-engine-friendly" title="Search-Engine Friendly">search-engine friendly</a>.</p>
<p>Place the main content of your News Item in the <strong>Body Text</strong> field.</p>
<div><img alt="News: Title, Description, BodyText" class="image-inline" src="../images/news-title.png/image_large" /></div>
<h2>News Item: Image and Caption</h2>
<p>You can add an <strong>Image</strong> and <strong>Image Caption</strong> to your News Item using the fields below the Body Text.</p>
<div><img alt="News: Add Picture" class="image-inline" src="../images/news-image.png/image_large" /></div>
<h2>News Item: Save</h2>
<p>Now is a good time to save your work:</p>
<div><img alt="Event: Save" class="image-inline" src="../images/event-save.png/image_preview" /></div>
<h2>News Item: Saved Changes</h2>
<p>Below is how a <strong>News Item</strong>'s Title, Summary, Body Text, Image, and Image Caption appear in Plone once its <strong>Saved</strong>. Your site administrator may have styled your News Items to appear slightly differently.</p>
<div><img alt="News: Image and Caption in Place" class="image-inline" src="../images/news-image-in-place.png/image_large" /></div>
<h2>News Item: Edit</h2>
<p>To continue editing your News Item, click <strong>Edit</strong>:</p>
<div><img alt="News: Edit" class="image-inline" src="../images/news-edit.png/image_large" /></div>
<h2>News Item: Internal Link</h2>
<p>If you wish to link to information elsewhere on the same site, this is called an <strong>Internal Link</strong>. To create an Internal Link, highlight the text you want to link, and click the Chain Link Icon in the Body Text editing area.</p>
<div><img alt="News: Select Internal Link" class="image-inline" src="../images/news-internal-link-select.png/image_large" /></div>
<h2>News Item: Internal Link</h2>
<p>In the box that opens, use the <strong>Search</strong> feature in the left column to find the content to which you want to link.</p>
<p>Select the button next to the content in the middle column of the box (in this case, Finch Behavior Explained).</p>
<p>Then click Insert at the bottom of the box.</p>
<div><img alt="insert internal link in plone 4.3" class="image-inline" src="../images/internal-link-4.3" /></div>
<h2>News Item: External Link</h2>
<p>A link to another website is called an <strong>External Link</strong>. To make an External Link from your News Item, highlight the text you want to link and click the Chain Link icon.</p>
<div><img alt="News: Select External Link" class="image-inline" src="../images/news-external-link-select.png/image_large" /></div>
<h2>News Item: External Link</h2>
<p>In the box that opens, place the web address in the field under <strong>External Link</strong>.</p>
<p>Click <strong>Preview</strong>, and you will see the page to which you are linking in the window below the web address field. This Preview demonstrates that the link is working—that is, the page hasn't been moved or deleted.</p>
<p>Click <strong>Insert</strong> at the bottom of the box.</p>
<div><img alt="insert external link in plone 4.3" class="image-inline" src="../images/external-link-4.3" /></div>
<h2>News Item: Categorization</h2>
<p>As with Events and other content types, <strong>Categorization</strong> is very powerful. Categories can be used to make your News Item appear in different places on your site, depending on what your site administrator has set up.</p>
<div><img alt="News: Categorization" class="image-inline" src="../images/news-categorization-01.png/image_large" /></div>
<h2>News Item Tags</h2>
<p>Select <strong>Tags</strong> (Categories) for your News Item the same as you did for your Event.</p>
<p>Depending on your permission level on the site, you may or may not have the ability to add <strong>New tags</strong>.</p>
<div><img alt="news item tags in plone 4.3" class="image-inline" src="../images/news-tags-4.3" /></div>
<h2>News Item: Location</h2>
<p>You can also add a geographical <strong>Location</strong>, so that individuals doing web searches for that Location will be more likely to find your News Item.</p>
<div><img alt="Location" class="image-inline" src="../images/location.png/image_large" /></div>
<h2>News Item: Related Items</h2>
<p>Add Related Items just as you did with your Event.</p>
<div><img alt="Related Items" class="image-inline" src="../images/related-items.png/image_preview" /></div>
<h2>News Item: Related Items</h2>
<p>Select the checkbox next to the <strong>Related Item</strong> that you want associated with your News Item.</p>
<div><img alt="Related Items 02" class="image-inline" src="../images/news-related-items-02.png/image_preview" /></div>
<h2>News Item: Publishing and Expiration Dates</h2>
<p>As with Events, you can also set a <strong>Publishing Date</strong>.</p>
<div><img alt="News: Dates" class="image-inline" src="../images/news-dates.png/image_large" /></div>
<h2>News Item: Publishing and Expiration Dates</h2>
<p>If you want the News Item to disappear from public view eventually, specify an <strong>Expiration Date</strong>.</p>
<div><img alt="News: Publishing and Expiration Dates" class="image-inline" src="../images/news-dates-02.png/image_large" /></div>
<h2>Page</h2>
<ul>
<li>Your site's <strong>core content</strong></li>
<li>The <strong>main information your users need</strong>. The <strong>main tasks your users want to accomplish</strong>.</li>
<li>The information's pertinence does <i><strong>not</strong></i> hinge on a <strong>beginning or end date</strong></li>
</ul>
<h2>Page: Placement</h2>
<div><img alt="Site Tree: Pages" class="image-inline" src="../images/site-tree-pages.png/image_preview" /></div>
<h2>Page: Adding a Page</h2>
<div><img alt="Page: Add" class="image-inline" src="../images/page-add.png/image_preview" /></div>
<h2>Page: Structure</h2>
<p>The following page has content with no appropriate structuring (formatting) applied. Let's make some changes so that it is more readable and <a class="internal-link" href="../glossary/search-engine-friendly" title="Search-Engine Friendly">search-engine friendly</a>, not to mention more engaging to the reader...</p>
<div><img alt="Page Content: Normal Paragraphs All" class="image-inline" src="../images/plain-page-content.png/image_large" /></div>
<h2>Page: Headings</h2>
<p>Why are we making these parts of the page <strong>Headings</strong>? Why not just bold-face the text? On the web, readers don't read; they <strong><i>scan</i></strong>. <strong>Headings</strong> help the reader scan a page's content. They also help give an understanding of the <strong><i>hierarchy</i></strong> of the content presented on the page. <strong>Headings</strong> also <a class="internal-link" href="../glossary/search-engine-friendly" title="Search-Engine Friendly">search-engine friendly</a>; directing visitors using <i><strong>search engines</strong></i> to your content.</p>
<div><img alt="Page Content: Headers" class="image-inline" src="../images/page-headers.png/image_large" /></div>
<h2>Page: Lists</h2>
<p>Notice that the text in the last sentence of paragraph 3 is essentially a list of items. Converting this information into an <strong>Unordered List</strong> allows your readers to more easily scan the content.</p>
<div><img alt="Page Content: Unordered List" class="image-inline" src="../images/page-ul.png/image_large" /></div>
<h2>Page: Pull-Quote</h2>
<p>Right now, all the content of this page flows in a single column. That's not bad; however, placing appropriate content in a <strong>Pull Quote</strong> can make the page a bit more interesting and set off that content so that it is more noticeable for your readers.</p>
<p>Highlight the text you want to be a Pull Quote, and select <strong>Pull-quote</strong> from the <strong>Style</strong> menu.</p>
<div><img alt="Pull Quote 1" class="image-inline" src="../images/pull-quote-01.png/image_large" /></div>
<h2>Page: Pull-Quote</h2>
<p>The text will now appear in its own area with its own appearance, depending on how your site is styled.</p>
<div><img alt="Pull Quote 2" class="image-inline" src="../images/pull-quote-02.png/image_large" /></div>
<h2>Page: Other Style Elements</h2>
<p><strong>Plone has a number of other styles available by default; your site administrator may remove some of these, however:</strong></p>
<p>Always check your paragraphs to make sure they have the Style <strong>Normal paragraph</strong>.</p>
<p>The <strong>Literal</strong> will create a block of text in which each letter can be placed exactly. This is useful for displaying text that must be specifically formatted, such as poetry, or code.</p>
<p>The <strong>Call-out</strong> style creates a block of text styled in its own way so that the reader's attention is drawn to it. Its effect is similar to the <strong>Pull-quote</strong>'s, but it is styled differently.</p>
<p><strong>Clear floats</strong> is a style that your site administrator may use to place elements on a page. It is generally not used by content providers.</p>
<p><strong>Discreet</strong> creates smaller, more subtle text.</p>
<p><strong>Highlight</strong> adds a background color behind text, as though a highlighter has been drawn over it.</p>
<p>The <strong>Page Break (print only)</strong> allows you to insert a page break for printing purposes.</p>
<div><img alt="Styles 1" class="image-inline" src="../images/styles.png/image_large" /></div>
<h2>Page: Formatting Options</h2>
<p>In addition, there are a number of formatting options available, similar to what you see in word processing software. Your site administrator may have removed some of these, also:</p>
<div><img alt="Styles 2" class="image-inline" src="../images/styles-02.png/image_preview" /></div>
<h2>Page: The Last Word on Styles and Formatting</h2>
<ul>
<li> Use styles and formatting with a <strong><i>light touch</i></strong>. </li>
<li> It is very easy to over-style a web page. </li>
<li> This makes the page user-unfriendly and appearing cluttered. </li>
</ul>
<h2>Image</h2>
<ul>
<li>.jpg</li>
<li>.png</li>
<li>.gif</li>
</ul>
<h2>Image: Make it Web-Ready</h2>
<ul>
<li>72dpi</li>
<li>Reasonable Dimensions</li>
<li>Cropped Appropriately</li>
</ul>
<h2>Image: File Names</h2>
<p>Plone goes a long way in making up for bad file names. However, all files uploaded to the web, including <strong>Image</strong> files, should have web-friendly names.</p>
<p>To make a file name web-friendly, give it a <strong>short</strong>, <strong>readable</strong>, <strong>all-lower case</strong> file name. Use <strong>no spaces or capital letters</strong>. Use <strong>hyphens</strong> (and no spaces) to parse out multiple-word file names (my-pup.png), not underlines.</p>
<h3 class="no-indent">Yes</h3>
<ul>
<li>tree.jpg</li>
<li>nice-tree.jpg</li>
</ul>
<h3 class="no-indent">No</h3>
<ul>
<li>TREE.JPG</li>
<li>tree.JPG</li>
<li>A Very Nice Tree.jpg</li>
<li>a_very_nice_tree_in_our_yard.jpg</li>
</ul>
<h2>Image: Adding an Image</h2>
<p>Add your images to the <strong>Images</strong> folder provided by your site administrator.</p>
<div><img alt="Image: Add" class="image-inline" src="../images/image-add.png/image_large" /></div>
<p> </p>
<h2>Image: Title and Description</h2>
<p> </p>
<div><img alt="Image: Add 02" class="image-inline" src="../images/add-image-02.png/image_large" /><br /></div>
<h2>Image: Your Recently Added Image</h2>
<div><img alt="Image: Add 03" class="image-inline" src="../images/add-image-03.png/image_large" /></div>
<h2>Image: Adding an Image to a Content Item</h2>
<p>Now that you've uploaded an image, let's add it to a page.</p>
<p>To add an image to a content item such as a Page, use the <strong>Image</strong> icon in the editing area:</p>
<div><img alt="Image: Icon in Editing Environment" class="image-inline" src="../images/image-icon-in-editing-environment" /></div>
<h2>Image: Searching and Placing</h2>
<p>This opens a box in which you can search for, and select your Image. Once you make a selection, a preview appears so that you can make sure you have selected the correct Image.</p>
<div><img alt="this image used on training page at http://weblion.psu.edu/services/documentation/bootcamp-beginners/content-types/." class="image-inline" src="../images/insert-image-4.3" /></div>
<p> </p>
<h2>Image: Content-Specific Alt Tag</h2>
<p>Note that the Image's <strong>Description</strong> appears here as well. The Description serves as the Alt Tag for the Image. You can change this Description to make it more closely related to the content of the Page, if you wish. This does not change the Image's original Description, just what the Page includes.</p>
<div><img alt="Image: Description: Content-Specific" class="image-inline" src="../images/image-description" /></div>
<h2>Image: Dimensions</h2>
<p>Finally, you can select from several size options:</p>
<div><img alt="Image: Dimensions" class="image-inline" src="../images/image-dimensions" /></div>
<h2>Image: Added to Content Item</h2>
<p>Once your Image is added, you can select it and change its size, alignment, and description.</p>
<p>You can <strong>remove the Image</strong> from your content by selecting the image and then hitting the delete key on your keyboard.</p>
<div><img alt="Image Added to Page" class="image-inline" src="../images/image-added" /></div>
<h2>File: Adding a File</h2>
<p>Add a file the same way that you add an image. Go to the folder on your site meant to contain files, and in the <strong>Add new</strong> menu, select <strong>File</strong>:</p>
<div><img alt="Adding a File, Step 1" class="image-inline" src="../images/adding-a-file-step-1/image_large" /></div>
<h2>File: Title and Description</h2>
<p>Give your file a <strong>Title</strong> that matches the title of your document. It's good for your users if you add other helpful information in your title, such as indicating that it is a booklet, or a flyer, and whether it is a PDF, PowerPoint, or other file type.</p>
<p>Provide a brief <strong>Description</strong> that gives further helpful information about your file. Remember, a good <strong>Title</strong> and <strong>Description</strong> helps users—including yourself—find this content on your site.</p>
<p>Upload your file, and <strong>Save</strong>.</p>
<div><img alt="Add a File, Step 2" class="image-inline" src="../images/add-a-file-step-2" /></div>
<h2>Files: Your Recently Added File</h2>
<p>Once you have added the file, you can use the <strong>Edit</strong> tab to modify the <strong>Title</strong> and <strong>Description</strong> or upload a file to replace the existing one.</p>
<div><img alt="Add a File, Step 3" class="image-inline" src="../images/add-a-file-step-3" /></div>
<h2>Links: Adding a Link</h2>
<p>The <strong>Link</strong> Content Type can be handy if you want to add items to folder contents and/or navigation that are links to<br />- External Web pages<br />- Items in another section of the same site.</p>
<p>For example, in your News folder, you may want the option of listing news stories published elsewhere:</p>
<div><img alt="Add Link 01" class="image-inline" src="../images/add-link-01/image_large" /></div>
<h2>Links: Title, Description, URL</h2>
<p>Most of the time you will want to give your Link the <strong>Title</strong> of the Web page or Item to which it is linking.</p>
<p>Provide a <strong>Description</strong> that will help explain what the link is about and that will aid in Web searches.</p>
<p>If it is a link to an external Web site, provide the entire URL, including the <strong>http://</strong>.</p>
<p>If you are linking to a page elsewhere on the <i><strong>same</strong></i> Web site, provide just the path in the URL field. For example, if the item's full URL is <strong>http://chickadees.footiepajamas.com/nesting/traits</strong>, the URL field should contain just <strong>/nesting/traits/</strong> and nothing else.</p>
<p><strong>Save</strong> your work once you've populated these three fields.</p>
<div><img alt="Add Link 02" class="image-inline" src="../images/add-link-02/image_large" /></div>
<h2>Links: Publishing</h2>
<p>Remember to <strong>Publish</strong> your link when you are ready for the public to see it.</p>
<div><img alt="Add Link 03" class="image-inline" src="../images/add-link-03" /></div>
<h2>Links: Published Link</h2>
<p>Your Published Link will appear in the Folder's listing and navigation just like any other Content Type.</p>
<div><img alt="Add Link 04" class="image-inline" src="../images/add-link-04/image_large" /></div>
<h2 class="training">Questions?</h2>
<div class="training">
<h5 align="right"><a class="internal-link" href="folders/presentation_view" title="Folders and their Contents">next...</a></h5>
</div>
</div>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-03-17T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/ploneformgen">
    <title>PloneFormGen</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/ploneformgen</link>
    <description>The Awesomest Product Ever</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="training">
<h2>Build Your Own Forms</h2>
<p>Here's what's great about the add-on product <a class="external-link" href="http://plone.org/products/ploneformgen">PloneFormGen</a>:</p>
<ul>
<li>Create online forms anywhere on your site</li>
<li>No programming required</li>
</ul>
<h2>Adding a Form Folder</h2>
<p>To create an online form using PloneFormGen, first add a Form Folder where you want the form to reside on your site.</p>
<img alt="Adding a Form Folder" class="image-inline" src="../images/add-form-folder-01" />
<h2>Adding a Form Folder: Title and Description</h2>
<p>Provide a <b>Title</b> and <b>Description</b>, just as you do with any Content Type. The <b>Title</b> and <b>Description</b> are what users will see in your site's navigation.</p>
<img alt="Title and Description" class="image-inline" src="../images/add-form-folder-02" />
<h2>Adding a Form Folder: Further Customization</h2>
<p>Next, customize some of the basics of your form.</p>
<p>Do you want to show a <b>Reset Button</b> that allows users to clear all their data and start over? If so, check the box next to this option and indicate what <b>Label</b> you want users to see next to this button.</p>
<p>By default, you get a <b>Mailer Action Adapter</b> with your form. This allows you to e-mail data collected by the form to one or more recipients. You can add other <b>Action Adapters</b> later if you need them.</p>
<p>You also get a <b>Thanks  Page</b> in your Form Folder by default. This is the page that users are sent to once they submit the form. You can edit this <b>Thanks Page</b> or add a new one. You can also opt to not have a <b>Thanks Page</b>.</p>
<p>If the form needs to be submitted by SSL (Secure Socket Layer) for security reasons, your sysem administrator will need to configure your server so that you can select the F<b>orce SSL connection</b> option.</p>
<img alt="More Form Customizations" class="image-inline" src="../images/add-form-folder-03" />
<h2>Adding a Form Folder: Prologue and Epilogue</h2>
<p>Add the <b>Form Prologue</b> text that you want the user to see above the form fields, and the <b>Form Epilogue</b> text that the user will see after the form fields, and <b>Save</b> your work. You can change any of these settings later if you need to.</p>
<img alt="Prologue and Epilogue" class="image-inline" src="../images/add-form-folder-04" />
<h2>Basic Form</h2>
<p>You now have a basic form with three default fields: <b>E-mail</b>, <b>Subject</b>, and <b>Comments</b>.</p>
<img alt="Newly added form folder using FormGen. Just the default fields at this point." class="image-inline" src="../images/added-form-folder" />
<h2>Editing Basic Settings</h2>
<p>To change any of the settings you just created, click the Form Folder's <b>Edit</b> tab.</p>
<img alt="Edit Form Folder" class="image-inline" src="../images/edit-form-folder" />
<h2>Adding More Fields</h2>
<p>Use the <b>Add new...</b> tab to add more fields to your form.</p>
<img alt="Add New Form Fields" class="image-inline" src="../images/add-new-form-fields" />
<h2>Common Field Types</h2>
<ul>
<li>String</li>
<li>Text</li>
<li>Select</li>
<li>Multi-Select</li>
<li>Checkbox</li>
</ul>
<h2>More Field Types</h2>
<ul>
<li>Lines (List)</li>
</ul>
<ul>
<li>Rating Scale (Multiple Radio Buttons)</li>
<li>Rich Text</li>
<li>(Whole) Number </li>
</ul>
<ul>
<li>Date/Time</li>
</ul>
<ul>
<li>File Upload</li>
</ul>
<ul>
<li>Password</li>
</ul>
<h2>String</h2>
<p><b>String Fields</b> are simple one-line text boxes; they're extremely common in forms. Use a <b>String Field</b> for data such as First Name, Last Name, E-mail, Phone, and the like.</p>
<p>In the <b>Field Label</b> field, indicate what information the user should provide. You can explain this further and provide instructions in the <b>Field Help</b> field.</p>
<p>Check the <b>Required</b> box if you want the user to have to provide the information.</p>
<p>Check the <b>Hidden</b> box if this field is being prepopulated and it's not necessary for the user to see it (for instance, if the form is for logged-in users and is automatically collecting the e-mail and user name).</p>
<img alt="Forms: String Field 01" class="image-inline" src="../images/forms-string-field-01" />
<h2>String: Default, Max Length, Size</h2>
<p>Use the <b>Default</b> field if it makes sense to prepopulate the form field with information that you would like to suggest to the user.</p>
<p>Make sure the <b>Max Length</b> is large enough to accommodate the information users will provide. For instance, you wouldn't want a phone number field that is 5 characters in length.</p>
<p><b>Size</b> controls the size (in numbers of characters) of the field that the user sees. Make the size large enough so that the user can see most, if not all, of the information they are typing.</p>
<img alt="Form: String Field 02" class="image-inline" src="../images/form-string-field-02" />
<h2>String: Validator</h2>
<p>The <b>Validator</b> menu is immensely useful. You can make sure that the user enters a valid e-mail address, phone number, zip code, website address, and so on. Adding Validators ensures that you will collect more useful data.</p>
<img alt="Forms: String Field 03" class="image-inline" src="../images/forms-string-field-03" />
<h2>Text</h2>
<p>A <b>Text Field</b> is similar to a String Field, except it's larger, and the user can add several lines. Text Fields are good for comments and other single-paragraph kinds of information.</p>
<p>When adding a Text Field, you may choose the number of <b>Rows</b> the field should have and the <b>Max Length</b>, or maximum number of characters the user may input -- be careful not to throttle this back too severely, thus limiting the information you get and frustrating users.</p>
<p>You can also <b>Reject Text with Links</b> to help prevent spamming.</p>
<div><img alt="formgen: text field" class="image-inline" src="../images/formgen-text-field" /></div>
<h2>Select</h2>
<p>The <b>Select Field</b> gives you the option of presenting items as a <b>Selection list</b>, <b>Radio buttons</b>, or in a <b>Flexible</b> format that switches from radio buttons to a selection list if the number of items exceeds <i><b>three</b></i>.</p>
<div><img alt="formgen: select 01" class="image-inline" src="../images/formgen-select-01" /></div>
<h2>Select: User Interface</h2>
<p>The Select Field allows users to select one item.</p>
<div><img alt="formgen: select 02" class="image-inline" src="../images/formgen-select-02" /></div>
<h2>Multi-Select</h2>
<p>If you want users to be able to select more than one item, use the <b>Multi-Select</b> Field. You can opt for a <b>Selection list</b> or a <b>Checkbox list</b>.</p>
<div><img alt="formgen: multi-select" class="image-inline" src="../images/formgen-multi-select" /></div>
<h2>Checkbox</h2>
<p>You can also add individual <b>Checkbox</b> fields. Adding individual checkboxes gives you more options: You can make an item <b>Required;</b> check or uncheck the box by <b>Default;</b> add a <b>Validator</b> to alert the user if the box was left checked or unchecked; and replace the "0" and "1" in the <b>Display Strings</b> with "Yes" and "No," "True" and "False," "I plan to attend the Carrot Festival" and "I will not be attending the Carrot Festival," or whatever you like.</p>
<div><img alt="formgen: checkbox" class="image-inline" src="../images/formgen-checkbox" /></div>
<h2>Lines</h2>
<p><b>Lines</b> Fields are good for inputting simple lists, such as job titles, names of individuals attending an event, that sort of thing. You can specify the maximum number of <b>Rows</b>, or Lines that the user can input.</p>
<div><img alt="formgen: lines" class="image-inline" src="../images/formgen-lines" /></div>
<h2>Rating Scale</h2>
<p>Using the <b>Rating Scale</b> Field, you can set up evaluations or surveys. Place one question per line (for example, <i><b>These trainers are insanely brilliant</b></i>) in the <b>Questions</b> field, and adjust the <b>Answers</b> to suit your needs.</p>
<div><img alt="formgen: rating 01" class="image-inline" src="../images/formgen-rating-01" /></div>
<h2>Rating Scale: User Interface</h2>
<p>Users will see a horizontal Rating Scale for each Question, and a Radio Button for each Answer.</p>
<div><img alt="formgen: rating 02" class="image-inline" src="../images/formgen-rating-02" /></div>
<h2>Rich Text</h2>
<p>Provide a <b>Rich Text</b> Field if you want users to be able to style and format their information and include links and media.</p>
<div><img alt="formgen: richtext 01" class="image-inline" src="../images/formgen-richtext-01" /></div>
<h2>Rich Text</h2>
<p>The <b>Rich Text</b> Field provides users with the visual editor on your Plone site, so that they can format their content and add images, video embeds (if you allow these), and hyperlinks.</p>
<div><img alt="formgen: richtext 02" class="image-inline" src="../images/formgen-richtext-02" /></div>
<h2>Whole Number</h2>
<p>The <b>Whole Number</b> Field requires the user to enter a whole number, such as 1, 9, 243, and so on.</p>
<p>You can specify the allowed number range (<b>Minimum Acceptable Value</b> and <b>Maximum Acceptable Value</b>) -- useful for collecting information on the number of family members planning to attend an event, for instance.</p>
<p>You can also limit the size, or <b>Max Length</b>, of the field.</p>
<div><img alt="formgen: whole number" class="image-inline" src="../images/formgen-whole-number" /></div>
<h2>Date/Time</h2>
<p>The <b>Date/Time</b> Field allows you to <b>Show Time Selection Options</b> (as opposed to just the date) and indicate a <b>Starting </b>and<b> Ending Year</b>. Leave the <b>Ending Year</b> blank and indicate one or more <b>Future Years to Display</b> if you want the Ending Year to always be in the present or future (this saves having to update your form as years come and go).</p>
<div><img alt="formgen: date-time 01" class="image-inline" src="../images/formgen-date-time-01" /></div>
<h2>Date/Time: User Interface</h2>
<p>This gives the user a simple <b>Date/Time</b> Field:</p>
<div><img alt="formgen: date-time 02" class="image-inline" src="../images/formgen-date-time-02" /></div>
<h2>File</h2>
<p>The <b>File</b> field allows users to upload an image, pdf, or other file type. It's generally a good idea to specify a  <b>Maximum Upload Size</b> (in megabytes) so that users do not upload inappropriately large files.</p>
<div><img alt="formgen: file upload" class="image-inline" src="../images/formgen-file-upload" /></div>
<h2>File: User Interface</h2>
<p>Users get a simple browse-and-upload form field.</p>
<div><img alt="formgen: file upload 02" class="image-inline" src="../images/formgen-file-upload-02" /></div>
<h2>Password</h2>
<p>The <b>Password</b> field is a string field, but it displays <b>**********</b> as the user types, thus obfuscating the inputted information. This is useful for passwords and other sensitive data.</p>
<div><img alt="formgen: password field" class="image-inline" src="../images/formgen-password-field" /></div>
<h2>Your Form Data</h2>
<p>Being able to build an online form this easily is great. But what about collecting the data? Plone FormGen has two built-in ways to collect and save your data:</p>
<ul>
<li>Mailer Adapter</li>
<li>Save-Data Adapter</li>
</ul>
<h2>Mailer Adapter</h2>
<p>Whenever you create a FormGen form, you get a <b>Mailer Adapter</b> automagically. You will see the Mailer Adapter in the <b>Contents</b> view of your form folder. Click on it to view and edit.</p>
<div><img alt="formgen: mailer: default: 01" class="image-inline" src="../images/formgen-mailer-default-01" /></div>
<h2>Mailer Adapter: Default Settings</h2>
<p>In the <b>Default</b> settings, you can indicate the <b>Recipient's full name</b> and <b>Recipient's</b> <b>e-mail address. <i>This information is very important:</i></b> It is the name and address of the person who will receive the data whenever your form is submitted.</p>
<p>You also can change the <b>Title</b> of your Mailer Adapter, though there's usually no reason to do so.</p>
<div><img alt="formgen: mailer: default: 02" class="image-inline" src="../images/formgen-mailer-default-02" /></div>
<h2>Mailer Adapter: Addressing</h2>
<p>The Addressing section allows you to make further customizations to the Recipient's e-mail.</p>
<p><b>Extract Recipient From: </b>Leave this as <b>None</b> <i><b>... unless </b></i>you want to override the <b>Recipient's E-mail Address</b> in the <b>Default</b> settings.</p>
<p>Add as many <b>CC Recipients</b> and <b>BCC Recipients </b>e-mails as you like, separated by commas.</p>
<div><img alt="formgen: mailer: addressing: 01" class="image-inline" src="../images/formgen-mailer-addressing-01" /></div>
<h2>Mailer Adapter: Addressing</h2>
<p><b>Extract Reply-To From</b> is set to collect the e-mail address of the individual filling out the form (the <b>Your E-Mail Address</b> field). If you change this to another field, make sure to activate e-mail address verification on that field.</p>
<div><img alt="formgen: mailer: addressing: 02" class="image-inline" src="../images/formgen-mailer-addressing-02" /></div>
<h2>Mailer Adapter: Message</h2>
<p>Under the <b>Message</b> tab, you can customize the e-mail's subject, body, and form data.</p>
<p><b>Subject</b>: It's a good idea to change the default "Form Submission" to wording that is specific to your form. This makes it easier for recipients to sort and filter the incoming e-mails. You also have the option to extract the subject line from a field other than <b>Subject</b>.</p>
<p><b>Body (prepended):</b> This is text you can provide at the beginning of the e-mail, displayed before the sender and subject lines.</p>
<div><img alt="formgen: mailer: message: 01" class="image-inline" src="../images/formgen-mailer-message-01" /></div>
<h2>Mailer Adapter: Message</h2>
<p><b>Body (appended):</b> This text is displayed after the sender and subject line and before the form data.</p>
<p><b>Body (signature) </b>is displayed after the form data, at the end of the e-mail message.</p>
<p>Check <b>Include all fields</b> if you want all of the form's data to be displayed in the e-mail message. Or, you can use  <b>Show Responses</b> to choose which ones to display. Check <b>Include empties</b> if you want to show which fields the user left blank.</p>
<p>When you are creating your form, it's a good idea to set yourself up as the <b>Recipient</b> at first so that you can try these different settings and see what the e-mail message actually looks like.</p>
<div><img alt="formgen: mailer: message: 02" class="image-inline" src="../images/formgen-mailer-message-02" /></div>
<h2>Mailer Adapter: Message</h2>
<div><img alt="formgen: mailer: message: 03" class="image-inline" src="../images/formgen-mailer-message-03" /></div>
<h2>Mailer Adapter: Template</h2>
<p>Tasks under the <b>Template</b> tab require a knowledge of HTML, TALES, and Python programming. If you have knowledge of these, you can customize the <b>Mail-Body Template</b>. Learn more about customizing this template at <a class="external-link" href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/customizing-the-mailer-template">plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/customizing-the-mailer-template</a>.</p>
<div><img alt="formgen: mailer: template: 01" class="image-inline" src="../images/formgen-mailer-template-01" /></div>
<h2>Mailer Adapter: Template</h2>
<p>You also can indicate whether you want the body of the e-mail to be rendered in <b>HTML</b> (useful if you want to have the extra styling and formatting that HTML offers) or to be in plain <b>Text</b>.</p>
<p>Your site administrator would be the one to make any adjustments to <b>HTTP Headers</b> -- these headers carry lots of useful information about the the client browser, the requested page,  the host (server), and other data your site administrator might want to capture.</p>
<div><img alt="formgen: mailer: template: 02" class="image-inline" src="../images/formgen-mailer-template-02" /></div>
<h2>Mailer Adapter: Encryption</h2>
<div><img alt="formgen: mailer: encryption: 01" class="image-inline" src="../images/formgen-mailer-encryption-01" /></div>
<h2>Mailer Adapter: Overrides</h2>
<div><img alt="formgen: mailer: overrides: 01" class="image-inline" src="../images/formgen-mailer-overrides-01" /></div>
<h2>Mailer Adapter: Overrides</h2>
<div><img alt="formgen: mailer: overrides: 02" class="image-inline" src="../images/formgen-mailer-overrides-02" /></div>
<h2>Save-Data Adapter</h2>
<p>The <b>Save-Data Adapter </b>allows you to save form data in either a comma-delineated or tab-dileneated list. You can view this data online or download it to save in a spreadsheet or database.</p>
<div><img alt="formgen: save data 01" class="image-inline" src="../images/formgen-save-data-01" /></div>
<h2>Save-Data Adapter</h2>
<p>Once you add the Save-Data Adapter, you will find it in your form folder contents.</p>
<div><img alt="formgen: save data 02" class="image-inline" src="../images/formgen-save-data-02" /></div>
<h2>Save-Data Adapter</h2>
<p>Under the Display menu, you can choose either the <b>Tabular View</b>, which displays your data in a table, or the <b>Record View</b>, which shows the data as a list. The <b>Download View</b> gives you a link for downloading the data as a file.</p>
<div><img alt="formgen: save data 03" class="image-inline" src="../images/formgen-save-data-03" /></div>
<h2>Save-Data Adapter</h2>
<p>Use the <b>Click here to get the saved input</b> link to save your data file. You can then open the tab-delineated (.tsv) or comma-delineated (.csv) file in a text editor, or in spreadsheet software.</p>
<div><img alt="formgen: save data 04" class="image-inline" src="../images/formgen-save-data-04" /></div>
<h2>Overrides</h2>
<p>The <b>Overrides</b> tab offers even more possibilities for customization.</p>
<div><img alt="Form Overrides" class="image-inline" src="../images/form-overrides" /></div>
<h2>Overrides</h2>
<h3>Requires Coding</h3>
<ul>
<li> HTML</li>
<li>TAL/TALES</li>
<li>Python</li>
</ul>
</div>
<div class="training">
<h2>A Few Possible Customizations</h2>
<p>Using Overrides, here are a few of the customizations you can do:</p>
<ul>
<li><a class="external-link" href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/send-an-email-to-the-form-submitter">Send an e-mail to the form submitter</a></li>
<li><a href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/customize-the-from-address"> <span class="state-published">Customize the <b>From</b> address </span></a></li>
<li><a href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/setting-a-custom-redirect"> <span class="state-published">Set a custom redirect</span></a></li>
<li><a href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/customize-the-subject-line-with-dynamic-values"> <span class="state-published">Customize the subject line with dynamic values</span></a></li>
<li><a href="http://plone.org/products/ploneformgen/documentation/tutorial/customizing-ploneformgen/customizing-the-mailer-template"> <span class="state-published">Customize the mailer template</span></a></li>
</ul>
<h2>More FormGen Information</h2>
<ul>
<li><a class="external-link" href="http://groundwire.org/resources/articles/plone-form-gen">PloneFormGen Documentation at GroundWire</a> - Good Starting Point</li>
<li><a class="external-link" href="http://learnplone.org/documentation/video/ploneformgen-in-depth">Video: PloneFormGen in Depth</a></li>
<li><a class="external-link" href="http://plone.org/products/ploneformgen/documentation">PloneFormGen Documentation at Plone.org</a> - Includes Ways to Customize FormGen</li>
<li><a class="external-link" href="http://plone.org/products/ploneformgen">PloneFormGen's Official Product Page<br /></a></li>
</ul>
<h5 align="right"><a class="internal-link" href="contentwellportlets/presentation_view" title="ContentWellPortlets">next...</a></h5>
</div>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-11-05T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/portlet-management">
    <title>Portlet Management</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/portlet-management</link>
    <description>Display Content Anywhere On Your Site</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2>What is a Portlet?</h2>
<p>Portlets are areas you create to add and display content. Portlets can be added to the left and right of the center body area and can contain myriad content ranging from news, events, calendars, RSS feeds, collections, plain text, and more. Also, you can set properties and policies for showing the portlets.</p>
<div><img alt="Bucket of Monkeys" class="image-inline" src="../images/bucktofmonkeys.png" /></div>
<h3>Think of a portlet like a bucket!</h3>
<h2>Why Use a Portlet?</h2>
<ul>
<li>You have content you want to have special focus, like news.</li>
<li>You need to specify the configuration data for an item. - i.e. number of entries to show.</li>
<li>You want to give the content editors a choice about when and where to display content.</li>
<li>You'd like to show it only to some groups or users.</li>
</ul>
<ul>
</ul>
<h2>Portlet Hierarchy</h2>
<h3>When managing portlets sitewide, keep in mind that they are <i><b>inherited:</b></i></h3>
<ul>
<li>Portlets set up at the <b>Site Root </b>propagate down through the <b>entire site</b>.</li>
<li>Portlets set up at the <b>Folder level</b> propagate down through that <b>entire Folder</b>.</li>
<li>Portlets set up on a single <i><b>noncontainer</b></i> Content Item <i><b>do not</b></i> propagate.</li>
</ul>
<h2>Blocking Parent Portlets</h2>
<ul>
<li>If you want a different set of portlets or order of portlets for a particular section, you must use the <b>Block/unblock portlets</b> controls, to "block" the parent portlets. When you block Portlets, you  must explicitly add all the Portlets that you wish to see on the child  page.</li>
</ul>
<h3>Here is an example of Plone's portlet hierarchy:</h3>
<div><img alt="Portlet Hierarchy" class="image-inline" src="../images/portlethierarchy.png" /></div>
<p>You can see that the Navigation portlet propagates down through the  entire site. Recent Items is visible through the first and second level,  but has been blocked in the third. Documentation has added a Collection  portlet, and Tutorials and Videos have added Search.</p>
<h2>Managing Portlets</h2>
<p>To start creating and editing portlets, you must click on the <b>Manage Portlets link</b>. Usually, this is found at the bottom of the left and/or right columns. Under Manage Portlets, you can create new portlets, remove portlets, rename, and rearrange portlets.</p>
<div><img alt="Manage Portlets Link" class="image-inline" src="../images/manageportletslink.png" /></div>
<p>Once you click the link, you'll see:</p>
<h2>Plone's Portlet Control Panel</h2>
<div><img alt="Portlet Control Panel" class="image-inline" src="../images/portletcontrolpanel.png" /></div>
<h2>Adding a Portlet</h2>
<p>Click on the <b>Add Portlet</b> drop down box and choose the type of portlet you would like to add. We discuss the different options available in a moment.</p>
<div><img alt="Add Portlet Dropdown" class="image-inline" src="../images/addportletdropdown.png" /></div>
<p>Understand that you have the ability to work with portlets on both     the right and left side of the page. This is because there are left and     right columns. <b>Portlets will only appear on the side(s) that you add them</b>.</p>
<p>Also, there is no limit to how many times you can use a certain type     of portlet or an individual portlet, or a limit to how many total     portlets can be on a page.</p>
<h2>Portlet Types shipped with Plone</h2>
<ul>
<li>Calendar</li>
<li>Classic</li>
<li>Collection</li>
<li>Events</li>
<li>Login</li>
<li>Navigation</li>
<li>News</li>
<li>RSS Feeds</li>
<li>Recent Items</li>
<li>Review List</li>
<li>Search</li>
<li>Static Text</li>
</ul>
<h2>Calendar Portlet</h2>
<p>This simple, non-customizable portlet displays a small calendar of any events on the site.</p>
<div><img alt="Calendar Portlet" class="image-inline" src="../images/portletcalendar.png" /></div>
<h2>Classic Portlet</h2>
<p>A <b>Classic Portlet</b> is...</p>
<ul>
<li>In the manner of older versions of Plone</li>
<li>Created by your site administrator using a page template in the Zope Management Interface (ZMI) </li>
<li> Handy when you want a simple custom portlet that can be used anywhere on the site</li>
<li>For example, the <b>Need Help Now?</b> portlet at <a class="external-link" href="http://weblion.psu.edu/services/training-support/documentation/">weblion.psu.edu/documentation</a></li>
</ul>
<h2>Collection Portlet</h2>
<p>A <b>Collection Portlet</b> displays a Plone collection. Collection portlets can be used for jobs such as:</p>
<ul>
<li>Displaying topic-related news or events in different sections of your site</li>
<li>Creating custom navigation</li>
<li>Creating those below-the-footer displays of links, features, etc. Like at <a class="external-link" href="http://agsci.psu.edu/">agsci.psu.edu</a> </li>
</ul>
<h2>Portlet Header and Target Collection</h2>
<p>Give your <b>Collection Portlet</b> the title of your choice in the portlet header field. Then search for and select the <b>Target collection</b>—that's the collection whose results you want displayed in your portlet.</p>
<div><img alt="Add Collection Portlet" class="image-inline" src="../images/portletcollection01.png" /></div>
<h2>Limit, Randomization, Link, and Dates</h2>
<p>In the <b>Limit</b> field, you can specify how many items you want  displayed in the collection portlet—if you do decide to limit the  display, you may want to check the box next to <b>Show more... link</b> so that users can get to the rest of the items in the collection.</p>
<p>You can randomize the display by checking the box next to <b>Select random items</b>.</p>
<p>If you want the publication dates of items to be visible, check the box next to <b>Show dates</b>.</p>
<div><img alt="Add Collection Portlet-2" class="image-inline" src="../images/portletcollection02.png" /></div>
<h2>Collection Portlet Display</h2>
<p>When you save your changes and click Return, you should see  your collection portlet display. If you do not see your portlet, check  your portlet settings, and check the original collection to make sure it  is displaying items.</p>
<div><img alt="Add Collection Portlet-3" class="image-inline" src="../images/copy_of_portletcollection03.png" /></div>
<h2>Events Portlet</h2>
<p>An <b>Events Portlet</b> displays upcoming events.  You can control how many are displayed as well as which workflow state  to show. For instance, if you choose <b>Published</b>, only published Events will show up in the portlet. If you want only certain events to show up, use a <b>Collection Portlet</b> instead.</p>
<div><img alt="Events Portlet" class="image-inline" src="../images/portletevents.png" /></div>
<h2>Login Portlet</h2>
<p>Selecting this adds a non-configurable <b>Login Portlet</b>. Don't be  confused if you do not see the login portlet once you add it. Only anonymous users can view the portlet.</p>
<div><img alt="Login Portlet" class="image-inline" src="../images/portletlogin.png" /></div>
<div>
<h2>Navigation Portlet</h2>
<p>The <b>Navigation Portlet</b> provides a structured navigation tree of the site or folder.</p>
<p>You can title the navigation portlet to reflect its location, or simply call it Navigation.</p>
<p>Next, indicate the <b>Root Node</b>, or folder on the site that you   want the portlet to navigate. If you want it to map out the entire site,   leave the root node field blank.</p>
<p>If you select <b>Include Top node</b>, your navigation portlet will list the <b>Title</b> of the site or folder at the top of the navigation tree.</p>
<div><img alt="Edit Navigation Portlet" class="image-inline" src="../images/editnavigationportlet.png" /></div>
<h2>Current Folder, Start Level, Depth</h2>
<p>You can indicate whether you want your navigation portlet to list only the items in the <b>current folder</b>.</p>
<p>When setting up site-wide navigation, you can indicate the <b>Start level</b>,  that is, the number of folder levels below the site where you want the  navigation to begin displaying. If you indicate 0 as the Start level,  the navigation will appear at the top of the site and everywhere below. 1  means it will not appear at the top of the site. And so on...</p>
<p>You can also control when the navigation tree should stop. A  navigation tree depth of 0 means that there is no limit. A navigation  tree depth of 1 indicates only the root folder, and so on.</p>
<p>You can edit your navigation portlet as many times as you need to until you get the navigation just right.</p>
<div><img alt="Edit Navigation Portlet-2" class="image-inline" src="../images/portletnavigation02.png" /></div>
<h2>Navigation Portlet Display</h2>
<div><img alt="Navigation Portlet Displayed" class="image-inline" src="../images/navportletdisplay.png" /></div>
</div>
<h2>News Portlet</h2>
<p>The <b>News Portlet </b>is much like the events portlet. You can chose the <b>Number of items to display</b> and the <b>Workflow state</b>. If you want to display only specific News Items, use a <b>Collection Portlet</b>.</p>
<div><img alt="News Portlet" class="image-inline" src="../images/portletnews.png" /></div>
<h2>RSS Portlet</h2>
<p>With <b>RSS Portlets</b>, it's simple to collect RSS feeds and display them  on your site.This is a great way to post material from blogs, news  portals, social media, and the like.</p>
<p>Choose a <b>Title</b> for the feed, the <b>Number of items to display</b>, provide the <b>URL of RSS feed</b>, and in the <b>Feed reload timeout</b> field, specify how frequently you want the feed to refresh on your site.</p>
<div><img alt="RSS Portlet" class="image-inline" src="../images/portletrss.png" /></div>
<h2>RSS Portlet Display</h2>
<p>You get a <b>More...</b> link for free, which leads to the full content of the item.</p>
<div><img alt="RSS Portlet-2" class="image-inline" src="../images/copy_of_portletrss02.png" /></div>
<h2>Recent Items Portlet</h2>
<p>The <b>Recent Items Portlet</b> displays a list of items on your site  with recent modification dates.</p>
<p>You can specify how many items to display in the Recent Items Portlet. An <b>All recent changes...</b> link leads to the full list.</p>
<div><img alt="Recent Items Portlet" class="image-inline" src="../images/portletrecent01.png" /></div>
<h2>Search Portlet</h2>
<p>The <b>Search Portlet </b>provides a search box. If you enable <b>Live Search</b>, users will see live results of their searches (if JavaScript is enabled on their browsers).</p>
<div><img alt="Search Portlet" class="image-inline" src="../images/portletsearch01.png" /></div>
<h2>Search Portlet Display</h2>
<p>The <b>Search Portlet </b>will search titles, descriptions, and body text of your site's content.</p>
<div><img alt="Search Portlet-2" class="image-inline" src="../images/portletsearch02.png" /></div>
<h2>Static Text Portlet</h2>
<p>The <b>Static Text Portlet</b> allows you to add content just as you  would on a page. Along with a <b>Title</b> (<b>Portlet header</b>) and <b>Body</b> <b>Text</b>, you get an optional<b> Border</b>, <b>Footer</b>, and <b>Details Link</b>.</p>
<div><img alt="Static Text Portlet" class="image-inline" src="../images/portletstatic.png" /></div>
<h2>Static Text Portlet Display</h2>
<p>Use <b>Static Text Portlets</b> for content that you cannot provide  using  the other portlet types. <b>Static Text Portlets</b> also are best for  content  that does not change frequently and content that doesn't get  reused in  various places on the site.</p>
<div><img alt="Static Text Portlet-2" class="image-inline" src="../images/portletstatic02.png" /></div>
<h2>Editing an Existing Portlet</h2>
<p>To <b>Edit</b>, <b>Reorder</b>, <b>Hide,</b> or <b>Show</b> portlets, be sure you are at the site level where the portlets actually were added.</p>
<p>To edit the properties of an existing portlet, click on the name of  the portlet. Each type of portlet will have different configuration  options available to it.</p>
<div><img alt="Editing Portlets" class="image-inline" src="../images/portletsedit.png" /></div>
<h2>Rearranging Portlets</h2>
<p>To rearrange your portlets, simply click the <b>blue up or down arrow</b>. This will affect the order your portlets are displayed on the page.</p>
<div><img alt="Rearranging Portlets" class="image-inline" src="../images/portletsreorder.png" /></div>
<h2>Removing Portlets</h2>
<p>To remove a portlet, click the<b> "X" </b>next to its name.</p>
<div><img alt="Removing Portlets" class="image-inline" src="../images/portletsremove.png" /></div>
<h2>Hiding Portlets</h2>
<p>In Plone 4, you can show/hide portlets using the associated show/hide links present.</p>
<div><img alt="Hiding Portlets" class="image-inline" src="../images/portletshide.png" /></div>
<h2>Showing a Portlet</h2>
<p>When you're ready to use the portlet again, click <b>Show</b>.</p>
<div><img alt="Show Portlet" class="image-inline" src="../images/portletsshow.png" /></div>
<h2>Beware the Default View</h2>
<h3>When you set about creating Portlets that you want to propagate, be careful to that you are creating the Portlet at the <b>Site Root</b> or <b>Folder</b> and not at the <b>Default View</b>:</h3>
<ul>
<li>my-site.edu/<b>front-page</b> is <i><b>not</b></i> the Site Root. my-site.edu/ <i><b>is</b></i>. </li>
<li>my-site/cheeses/<b>cheese-home</b> is <i><b>not</b></i> the Folder Level. my-site/cheeses/ <i><b>is</b></i>.</li>
</ul>
<h2>Check the URL</h2>
<p>When setting up Portlets that you want to propagate through an entire folder, look at the URL after following the <b>Manage Portlets</b> link. If the default view is visible in the URL, remove it before adding the portlets. In the example below, <b>tasty-suet-cakes</b> is the Default View for the Folder <b>/feeding/</b>. Simply shave <b>/tasty-suet-cakes</b> off the URL, and you're good to go.</p>
<ul>
<li><b>You're at the Default View:</b> http://chickadees.org/feeding/<b>tasty-suet-cakes/</b>@@manage-portlets</li>
<li><b>You're at the Folder:</b> http://chickadees.org/feeding/@@manage-portlets</li>
</ul>
<h2>Blocking and Unblocking Portlets</h2>
<h3>Your content inherits <b>Portlet Settings</b> from the <i><b>Parent</b></i> container—the Folder that the content lives in, not folders farther upstream.</h3>
<p>You can <b>Block</b> these portlet settings:</p>
<div><img alt="Blocking Portlets" class="image-inline" src="../images/copy_of_portletsblocking01.png" /></div>
<p>In Plone 4, users can now see what's being blocked and what's being  inherited.</p>
<h2>Blocked Items are Grayed Out</h2>
<p>A blocked portlet will be grayed out on on the portlet  management screen:</p>
<div><img alt="Portlet Management Screen" class="image-inline" src="../images/portletmanagementscreen.png" /></div>
<h2>Which Portlets to Block</h2>
<p>When blocking and unblocking portlets, understand what those three different pulldown menus are about:</p>
<h3>Parent Portlets</h3>
<ul>
<li>Affects <i><b>all</b></i> portlets, including <b>Group</b> and <b>Content Type</b> <b>Portlets</b>.</li>
<li><i><b>But,</b></i> settings for<b> Group</b> and <b>Content Type</b> <b>Portlets</b> can override for these two portlet types.</li>
</ul>
<h3>Group Portlets</h3>
<ul>
<li>Created by your Site Manager for <b>Groups</b> of <b>Users</b>.</li>
<li><b>Block</b> and <b>Do not block</b> override parent settings.</li>
</ul>
<h3>Content Type Portlets</h3>
<ul>
<li>Assigned in the Plone Control Panel to specific <b>Content Types </b>by your Site Manager<b> </b>.</li>
</ul>
<ul>
<li><b>Block</b> and <b>Do not block</b> override parent settings.</li>
</ul>
<h2>ContentWellPortlets</h2>
<p><a class="external-link" href="http://plone.org/products/contentwellportlets">ContentWellPortlets</a> is a very handy add-on Plone product that allows you to place portlets   above the main content, below the main content, and in the footer area.</p>
<div><img alt="Content Well Portlets" class="image-inline" src="../images/contentportlets.png" /></div>
<h2>ContentWellPortlets Controls</h2>
<p>You can add up to six portlets in these areas.</p>
<div><img alt="Content Well Portlet Controls" class="image-inline" src="../images/contentwellportletcontrols.png" /></div>
<h5 align="right"><a class="internal-link" href="users-groups-permissions/presentation_view" title="Users, Groups, and Permissions">next...</a></h5>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Beth Phillips</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: beginners</dc:subject>
    
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-06-01T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>


  <item rdf:about="http://weblion.psu.edu/services/documentation/bootcamp-beginners/users-groups-permissions">
    <title>Users, Groups, and Permissions</title>
    <link>http://weblion.psu.edu/services/documentation/bootcamp-beginners/users-groups-permissions</link>
    <description>Controlling who can do what on your Plone site</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2>Users</h2>
<ul>
<li><b>Anonymous<br /></b> 
<ul>
<li>Those who <i>cannot</i> log into Your Plone Site.</li>
</ul>
</li>
<li><b>Logged-In </b>(or<b> Authenticated)<br /></b> 
<ul>
<li>Listed as <b>Users</b> in Plone Control Panel. </li>
<li>Their default Role is <b>Member</b>.</li>
</ul>
</li>
</ul>
<h2>Groups</h2>
<ul>
<li>A set of one or more <b>Users</b>.</li>
</ul>
<h2>Roles</h2>
<ul>
<li><b>Global Roles:</b> Apply to <b>Entire Site</b>. Can see these listed in Plone Control Panel.</li>
<li><b>Local Roles:</b> Apply to a <b>Section</b> of the site.</li>
</ul>
<h2>Permissions</h2>
<ul>
<li>Roles come with <b>Permissions</b><br /> 
<ul>
<li>The ability to Edit, Publish, Delete, and so on.</li>
</ul>
</li>
</ul>
<h2>Granting Roles (and Therefore Permissions)</h2>
<ul>
<li>You can grant Roles to individual <b>Users</b>.</li>
<li>But it's usually better to grant Roles to <b>Groups</b>.</li>
</ul>
<h2>Sharing</h2>
<ul>
<li>A <b>Local</b> way of granting Roles and Permissions.<br /> 
<ul>
<li>Share a Folder, Page, Collection, etc. with a <b>Group</b>...</li>
<li>...and can grant the Group <b>Permissions</b> on that item.</li>
</ul>
</li>
</ul>
<h2>Example</h2>
<ul>
<li>You have a folder on your site called <b>Training</b>.</li>
<li><b>Authenticated User Rose Pruyne</b> needs to add and edit content in this <b>Training</b> folder.</li>
<li>You, the site manager, create a Group called <b>Training Content Providers</b>.</li>
<li>You add Authenticated User Rose Pruyne to the <b>Group </b>Training Content Providers.</li>
<li>You <b>Share</b> the Training folder with this Group. <br /> 
<ul>
<li>You grant <b>Add</b> and <b>Edit</b> privileges to this Group<b></b>.</li>
</ul>
</li>
</ul>
<h2>Why Groups Instead of Individual Users?</h2>
<ul>
<li>Who can do what?? Where?? </li>
<li>Keeping track of Groups is <b><i>much</i></b> easier.</li>
</ul>
<h2>Recommended Practice</h2>
<ul>
<li>Assign Users to <b>Groups</b>.</li>
<li>Assign Groups to areas of the site, using <b>Sharing</b>.</li>
<li>Do not assign Roles to individual users.</li>
<li>Do not assign individual Users to areas of the site. </li>
</ul>
<h2>Exercise</h2>
<ul>
<li>Add a new Folder on your site and call it <b>Documentation</b>.</li>
<li>Add a new <b>User</b> to your site.</li>
<li>Create a Group called <b>Documentation Content Providers</b>.</li>
<li>Add the new User to this Group.</li>
<li>Give this Group Add and Edit permissions </li>
<li>Open your site in another browser and log in as the new User. Try to add a page to the Documentation Folder.</li>
</ul>
<div align="right">
<h5 align="right"><a class="internal-link" href="information-architecture/presentation_view" title="Information Architecture">next...</a></h5>
</div>]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Rose Pruyne</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>documentation: plone training: bootcamp</dc:subject>
    
    
      <dc:subject>documentation: content management</dc:subject>
    
    <dc:date>2010-07-09T04:00:00Z</dc:date>
    <dc:type>Page</dc:type>
  </item>





</rdf:RDF>
