webteam:webplan:2011:section6_recommendations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
webteam:webplan:2011:section6_recommendations [2011/09/01 12:23] – [Files] jimcraner | webteam:webplan:2011:section6_recommendations [2011/09/07 18:18] – added knowledge management notes to section F jimcraner | ||
---|---|---|---|
Line 131: | Line 131: | ||
This knowledge base could be as complex as a dedicated knowledge management application or as simple as a dedicated set of wiki pages kept up-to-date and highlighted for website visitors. | This knowledge base could be as complex as a dedicated knowledge management application or as simple as a dedicated set of wiki pages kept up-to-date and highlighted for website visitors. | ||
+ | |||
+ | During the website visitor survey, respondents were given a list of existing website sections/ | ||
+ | |||
+ | These three areas - docs, wiki, and mailing list - can ideally be used as three different “tiers” or “phases” of collaboration and community knowledge management. For instance, a discussion about a particular problem or feature may take place on the mailing list, where it appears in the archives. Information that is deemed especially valuable in the mailing list archives might be moved by an enthusiastic website contributor into the unofficial documentation stored on the wiki. Documentation Interest Group members may then regularly review popular wiki pages to determine if they are suitable for inclusion in the “official” documentation where they would most likely be accessed by the largest number of potential users. | ||
+ | |||
+ | This is a type of knowledge management is a form of curation, by which people in different roles or contexts manually move knowledge from a limited discussion context into a context accessible to all on the website. However, website visitors increasingly rely on search, especially for finding specific information within a broad topic such as Evergreen. | ||
+ | |||
+ | ==== G. Implement a support forum as an alternative to the mailing list and IRC for user-to-user support ==== | ||
+ | |||
+ | Evergreen users seeking community support currently use the mailing list and the IRC channel. | ||
+ | |||
+ | ==== H. Implement a " | ||
+ | |||
+ | As a collaborative open source software project, the Evergreen community has a demonstrated history of organizations successfully working together to build software. | ||
+ | |||
+ | ==== I. Implement personalization tools on the website to increase effectiveness ==== | ||
+ | |||
+ | Because many EG community members perform multiple roles in their EG deployment, and because of the increase of content related to EG, we recommend the implementation of website personalization tools to help increase visitors' | ||
+ | |||
+ | *a " | ||
+ | *a rating tool which would allow registered visitors to rate the usefulness of certain pages, thereby showing the most popular or helpful pages | ||
+ | *a notification mechanism to allow registered visitors to sign up for email notifications of new content matching certain criteria | ||
+ | *a way to focus the display of website content on a visitor' | ||
+ | |||
Line 137: | Line 161: | ||
{{: | {{: | ||
- | {{: | + | {{: |
- | {{:webteam:eg_newsite_wireframes_20110831a.pdf|EG New Website Platform - Functional Wireframes - 2011-08-31}} | + | {{:webteam:eg_newsite_wireframes_20110905b.pdf|EG New Website Platform - Functional Wireframes - 2011-09-05}} |
webteam/webplan/2011/section6_recommendations.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1