Differences

This shows you the differences between two versions of the page.

--- webteam:webplan:2011:section6_recommendations [2011/08/16 17:00] – jimcraner
+++ webteam:webplan:2011:section6_recommendations [2011/09/07 18:09] – added more feature recos to list jimcraner
@@ Line 86: / Line 86: @@
   * Single sign-on, single sign-in
+  * Centralized search index encompassing all content
   * Easier analytics and statistics gathering
   * Easier to maintain consistent branding and visual treatment
@@ Line 131: / Line 132: @@
 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.
+==== G. Implement a support forum as an alternative to the mailing list and IRC for user-to-user support ====
-===== Files =====
+Evergreen users seeking community support currently use the mailing list and the IRC channel.  Some users are more comfortable using a web-based interface for support interactions -- or for finding relevant information in historical archives of those interactions.  In addition, support forum posts would automatically be archived and indexed by the content management system and could take advantage of tagging/categorization, identity/profile connection, and other features not available to the web-based mailing list and IRC transcript archives.
-{{:webteam:eg_sysarch-logical_20110509.pdf|EG Web Content Environment (Logical) - 2011-05-09}}
+==== H. Implement a "feature percolator" for collaborative development of feature/enhancement ideas ====
+As a collaborative open source software project, the Evergreen community has a demonstrated history of organizations successfully working together to build software.  The "feature percolator" application proposed by the Web Team would allow community members to submit their ideas to a community forum for collaborative discussion and development.  In addition, community members participating in the discussion of each idea would be able to communicate their willingness, if any, to sponsor the development and implementation of that idea.  This process is hoped to foster relationships between community members leading to greater collaboration and improvement of the Evergreen 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' effective use of the website.  These tools could include:
+  *a "favorite" tool to allow registered visitors to bookmark certain pages within the site
+  *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's criteria, such as audience target or category
+===== Files =====
 {{:webteam:eg_sitemap_proposed_20110509.pdf|EG Proposed Site Map Revision - 2011-05-09}}
-{{:webteam:eg-newsite-wireframes-20110510d.pdf|EG Proposed Functional Wireframes - 2011-05-10}}
+{{:webteam:eg-content_arch-20110905b.pdf|EG New Website Platform - Logical Content Architecture - 2011-09-05}}
+{{:webteam:eg_newsite_wireframes_20110905b.pdf|EG New Website Platform - Functional Wireframes - 2011-09-05}}