<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Jivespace: Message List - Guiding users to content - any help or best practices?</title>
    <link>http://www.jivesoftware.com/jivespace/community/developer?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 23 Apr 2008 20:01:39 GMT</pubDate>
    <generator>Jive SBS 3.0.8 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-04-23T20:01:39Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Guiding users to content - any help or best practices?</title>
      <link>http://www.jivesoftware.com/jivespace/message/94783?tstart=0#94783</link>
      <description>&lt;!-- [DocumentBodyStart:fcec08a4-206f-4681-927a-9bb3af6f3e34] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;We've gone ahead and created something we're calling a "Signpost" widget.&amp;nbsp; HTML editing, with no revision tracking, is not really an option for many of our project leaders (the people who edit space overview tabs in our world).&amp;nbsp; Our Pubs people would love the power of HTML editing for every document they write (;&amp;gt;) but other users cringe at that and want WYSIWYG for everything.&lt;br/&gt;&lt;br/&gt;Anyway, our Signpost widget allows users to have any number of groupings of links with a custom name per link and custom title on each instance of the widget.&amp;nbsp; It's editable like any other widget.&amp;nbsp; So far our users really like it - and they're sending us many more requests to expand the functionality.&lt;br/&gt;&lt;br/&gt;We weren't able to accomplish this as a plugin or we'd share it.&amp;nbsp; We're on 1.10.5 - not sure at this time when we'll be able to upgrade to 2.x.&amp;nbsp; Maybe in the future we could share this.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:fcec08a4-206f-4681-927a-9bb3af6f3e34] --&gt;</description>
      <pubDate>Wed, 23 Apr 2008 20:01:39 GMT</pubDate>
      <author>communities@jivesoftware.com</author>
      <guid>http://www.jivesoftware.com/jivespace/message/94783?tstart=0#94783</guid>
      <dc:date>2008-04-23T20:01:39Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Guiding users to content - any help or best practices?</title>
      <link>http://www.jivesoftware.com/jivespace/message/94483?tstart=0#94483</link>
      <description>&lt;!-- [DocumentBodyStart:6106e590-320c-42ee-a423-93c71d9a9ee6] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;We've been doing this mostly with widgets (html widget with links to key content). One example is on the &lt;a class="jive-link-external-small" href="community/developer/clearspace/plugins"&gt;plugin page&lt;/a&gt; People can get pretty creative with the existing widgets, especially in Clearspace 2.0 where we have a few more widgets available. In most cases, we've been able to use the existing widgets to do what you described without having to develop any new widgets.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:6106e590-320c-42ee-a423-93c71d9a9ee6] --&gt;</description>
      <pubDate>Mon, 14 Apr 2008 22:41:39 GMT</pubDate>
      <author>communities@jivesoftware.com</author>
      <guid>http://www.jivesoftware.com/jivespace/message/94483?tstart=0#94483</guid>
      <dc:date>2008-04-14T22:41:39Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Guiding users to content - any help or best practices?</title>
      <link>http://www.jivesoftware.com/jivespace/message/94388?tstart=0#94388</link>
      <description>&lt;!-- [DocumentBodyStart:db4b74bc-900f-4aef-80c0-762244c57895] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Hello - &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Our deployment of Clearspace is a few months old now and more users are migrating into the system from our previous wiki/discussions/blogs platform.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Our users like many things about Clearspace but we've had some pretty strong criticisms about the lack of structure.&amp;nbsp; We've explained how we are using tags, tag groups and a feature called "Topics" that we developed, to apply metadata and use the metadata to generate different views/slices of content.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;What we are finding though is that users aren't married to structure and hierarchy just because they are familiar with it.&amp;nbsp; Rather, they want ways to guide users to specific content vs. just "recent" or "popular" content.&amp;nbsp; Here is an example:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Team X is a core project team and the work they do in their space is consumed by many other teams across the company.&amp;nbsp; To an extent those other teams also collaborate on the content, but in many ways they just consume it and use it in their own projects.&amp;nbsp; Team X wants a way to direct their many disparate users (some very casual, some more regular) to content that they need to see.&amp;nbsp; Understand that the consumers don't necessarily know what they need to see - doing a search isn't the answer because they don't know what to search on.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Team X wants to have sections on their Overview page for things like&amp;nbsp; "Start Here",&amp;nbsp;&amp;nbsp; "How to Get More Involved", "Current Work", "FAQ" etc.&amp;nbsp; as well as ways to promote specific subject areas and provide an organized drill into content&amp;nbsp; (e.g. is this content just a proposal or is it something the team has decided to do?). &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;They want to make their project more friendly and easily browseable for finding content.&amp;nbsp;&amp;nbsp; Some biting feedback we had was "It feels like a giant whiteboard with notes all over it" which is basically coming from frustration with producing work that must be consumed by a much larger community and not understanding how best to present things.&amp;nbsp; If their consumers (generally very frenzied field consultants and other product teams) get frustrated or overwhelmed by data, they won't use the system to get their information - they'll send email to someone for the answer. &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;So, we are looking at developing our own widgets for the Overview tab where users can list explicit links to content.&amp;nbsp; This has appeased some people but they are still looking for more.&amp;nbsp; Some requests have been: a tighter drill-in on content (like an advanced search on tag groups and tags so they can get to very specific information), a way to show content from a specific timeframe/release, a way to promote content or, for example, show that right now a particular document is "speculative" and not yet "what we are going to do".&amp;nbsp; Text in the page or tags could somewhat be used for the last item but there is some desire to have this data piece be more prominent than other metadata. &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway, that's a long list of a lot of stuff...&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="16px" src="http://www.jivesoftware.com/community/images/emoticons/wink.gif" width="16px"/&gt;&amp;nbsp;&amp;nbsp; If others have had the same issue or if you have some guidance or suggestions on space &amp;amp; content best practices or ways to help with this problem, they would be greatly appreciated!! &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks. &lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:db4b74bc-900f-4aef-80c0-762244c57895] --&gt;</description>
      <pubDate>Fri, 11 Apr 2008 01:19:55 GMT</pubDate>
      <author>communities@jivesoftware.com</author>
      <guid>http://www.jivesoftware.com/jivespace/message/94388?tstart=0#94388</guid>
      <dc:date>2008-04-11T01:19:55Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

