User Tools

Site Tools


webteam:webplan:2011:section6_recommendations

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
webteam:webplan:2011:section6_recommendations [2011/05/10 22:40]
jimcraner [Files]
webteam:webplan:2011:section6_recommendations [2011/09/07 18:19] (current)
jimcraner [F. Implement a knowledge base to easily store highly-relevant and frequently-accessed Evergreen technical information]
Line 14: Line 14:
 ** Creation of formal Evergreen Website Team**  ** Creation of formal Evergreen Website Team**
  
-A community website platform that supports the needs of a diverse community and fosters the growth of that community is not something that can be built and then left to run on its own.  We're recommending the formation of a formal Website Team, to be composed of self-selected community members, ​  and reporting to the Governance Committee until a formal Evergreen organizational structure can be put in place. ​ The twin primary goals of this Team would be to make short-term improvements to the website as well as plan long-term architecture improvement and maintenance operations. ​ This Team would actively and regularly seek out feedback and suggestions for direction from Evergreen community constituencies,​ including the Communications Committee, the developer community, DIG, new users and potential users, etc.  In addition, this team would be tasked with lowering any barriers to participation in the website and encouraging contributions from as many community members as possible.+A community website platform that supports the needs of a diverse community and fosters the growth of that community is not something that can be built and then left to run on its own.  We're recommending the formation of a formal Website Team, to be composed of self-selected community members, ​  and reporting to the Governance Committee until a formal Evergreen organizational structure can be put in place. ​ The twin primary goals of this Team would be to make short-term improvements to the website as well as plan long-term architecture improvement and maintenance operations. ​ This Team would actively and regularly seek out feedback and suggestions for direction from Evergreen community constituencies,​ including the Communications Committee, the developer community, DIG, new users and potential users, etc.  In addition, this team would be tasked with lowering any barriers to participation in the website and encouraging contributions from as many community members as possible.  Finally, this team would coordinate a schedule of maintenance and management duties for volunteers (e.g., conducting periodic reviews of curated content, performing website software updates, running link scanning tools to detect old or broken links, etc.).
  
 **Creation of Website Policies** **Creation of Website Policies**
Line 42: Line 42:
 Many of the strategic goals and requirements defined during this process involve the need for a system allowing as many community members as possible to easily contribute content to the community: documentation,​ files, useful resources, discussion, etc.  A modern community website platform would include easy-to-use,​ web-based content management tools for all community members to take advantage of.  ​ Many of the strategic goals and requirements defined during this process involve the need for a system allowing as many community members as possible to easily contribute content to the community: documentation,​ files, useful resources, discussion, etc.  A modern community website platform would include easy-to-use,​ web-based content management tools for all community members to take advantage of.  ​
  
-At the same time, there is a need for the community website to be well-organized and for highly-relevant information to be curated to a prominent position. ​ A well-designed website platform would provide powerful editorial capabilities for the Evergreen Website Team defined in the People & Process Recommendations.+At the same time, there is a need for the community website to be well-organized and for highly-relevant information to be curated to a prominent position, while deprecated information is archived or removed.  A well-designed website platform would provide powerful editorial capabilities for the Evergreen Website Team defined in the People & Process Recommendations.
  
 **2. Provide collaboration tools that allow community members to work together** **2. Provide collaboration tools that allow community members to work together**
  
-**3. Provide ​foundation ​for data-driven ​community ​applications**+Like most communities,​ the EG community uses combination of web-based development tools (software code and documentation repositories,​ development management, community wiki space), email (on various development and community-focused lists), and IRC (development,​ support, and community meetings). ​ The Web Team has identified some additional opportunities ​for web-based community ​tools, such as standard online forums (for discussion and/or support), an idea percolator (a workflow for identifying potential collaborators),​ and a voluntary contact directory of Evergreen community members (individuals and organizations).
  
-**4. Provide a foundation for integrating third-party data, software, and services**+**3. Provide a foundation for integrating third-party data, software, and services**
  
 There are a variety of requirements that involve interacting with third-party data, software, and services. ​ Many of these requirements are fairly straightforward,​ e.g.: There are a variety of requirements that involve interacting with third-party data, software, and services. ​ Many of these requirements are fairly straightforward,​ e.g.:
Line 54: Line 54:
   * allowing website visitors to easily post a link to the website to their Facebook profile   * allowing website visitors to easily post a link to the website to their Facebook profile
   * integrating website content and internal search with Google Analytics to help the Website Team gather data for continuous website improvement   * integrating website content and internal search with Google Analytics to help the Website Team gather data for continuous website improvement
-  * aggregating Evergreen-related content from third-party websites via RSS or API+  * aggregating Evergreen-related content from third-party websites via RSS or API, especially bug-tracking and development-management tools used by the developer community
  
 A community website platform can include many of these features "out of the box" or via relatively easy modular integration. A community website platform can include many of these features "out of the box" or via relatively easy modular integration.
Line 86: Line 86:
  
   * Single sign-on, single sign-in   * Single sign-on, single sign-in
 +  * Centralized search index encompassing all content
   * Easier analytics and statistics gathering   * Easier analytics and statistics gathering
   * Easier to maintain consistent branding and visual treatment   * Easier to maintain consistent branding and visual treatment
Line 121: Line 122:
   * create curated content collections (e.g., "​Migration Center"​ page linking to relevant resources for visitors seeking migration information)   * create curated content collections (e.g., "​Migration Center"​ page linking to relevant resources for visitors seeking migration information)
  
-===== Files =====+==== E. Implement an up-to-date list of Evergreen features that is searchable, sortable, and categorized. ​====
  
-{{:webteam:eg_sysarch-logical_20110509.pdf|EG Web Content Environment ​(Logical) - 2011-05-09}}+Lori Ayre is currently spearheading a team of community contributors working on a draft of this features list.  The present incarnation is a Google Docs spreadsheet embedded in the EG wiki here: 
 + 
 +http://evergreen-ils.org/​dokuwiki/​doku.php?​id=feature_list 
 + 
 +==== F. Implement a searchable and browsable knowledge base to easily store highly-relevant and frequently-accessed Evergreen technical information ==== 
 + 
 +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/​components and asked to identify those that they “most frequently” access. Unsurprisingly,​ the most commonly used sections of the site are the official documentation ​(produced by the Doc Interest Group), the unofficial documentation (produced by the community using the website'​s Dokuwiki functionality,​ and the mailing list archives. The Web Team had already identified these three content areas as containing almost the entire collective knowledge base of Evergreen. 
 + 
 +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. ​ Therefore, it is critical that all identified information sources are incorporated into a search corpus and that end-user search tools on the site are able to return useful results to user queries. ​ In addition, the website should be structured in a way that optimizes automated indexing by third parties such as Google. This will help ensure that the site is ranked as a valuable resource for those searching with off-site tools. 
 + 
 +==== 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. ​ 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. 
 + 
 +==== 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_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}} 
  
  
  
webteam/webplan/2011/section6_recommendations.1305081616.txt.gz · Last modified: 2011/05/10 22:40 by jimcraner

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.