webteam:webplan:2011:section6_recommendations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
webteam:webplan:2011:section6_recommendations [2011/05/10 21:40] – jimcraner | webteam:webplan:2011:section6_recommendations [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
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, | + | 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, |
**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, | 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, | ||
- | 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. | + | 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 | + | Like most communities, |
- | **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. | There are a variety of requirements that involve interacting with third-party data, software, and services. | ||
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 81: | Line 81: | ||
d. begin community outreach activities to encourage membership and participation in new online community platform | d. begin community outreach activities to encourage membership and participation in new online community platform | ||
- | ==== C. Integrate off-site sites and features into new community website platform where appropriate ==== | + | ==== B. Integrate off-site sites and features into new community website platform where appropriate ==== |
Benefits of centralization: | Benefits of centralization: | ||
* 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 101: | Line 102: | ||
As the Evergreen ecosystem continues to grow, relevant content will increasingly be found off-site. | As the Evergreen ecosystem continues to grow, relevant content will increasingly be found off-site. | ||
- | ==== D. Develop content structure and curated content for targeted audience roles: potential implementer/ | + | ==== C. Develop content structure and curated content for targeted audience roles: potential implementer/ |
One of the key functionality requirements for the website is the ability for users to browse and search for content specifically targeted at their specific role. To properly satisfy this requirement, | One of the key functionality requirements for the website is the ability for users to browse and search for content specifically targeted at their specific role. To properly satisfy this requirement, | ||
Line 111: | Line 112: | ||
* create curated content collections (e.g., " | * create curated content collections (e.g., " | ||
- | ==== E. Develop content structure and curated content for specific topics (circulation, | + | ==== D. Develop content structure and curated content for specific topics (circulation, |
One of the key functionality requirements for the website is the ability for users to browse and search for content based on a specific topic or keyword. | One of the key functionality requirements for the website is the ability for users to browse and search for content based on a specific topic or keyword. | ||
Line 121: | Line 122: | ||
* create curated content collections (e.g., " | * create curated content collections (e.g., " | ||
- | ===== 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 | + | 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/ | ||
+ | |||
+ | ==== 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/ | ||
+ | |||
+ | 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' | ||
+ | |||
+ | |||
+ | |||
+ | ===== Files ===== | ||
{{: | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
webteam/webplan/2011/section6_recommendations.1305078010.txt.gz · Last modified: 2022/02/10 13:34 (external edit)