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/05/10 22:40] – [Files] jimcraner | webteam:webplan:2011:section6_recommendations [2011/09/01 12:23] – [Files] jimcraner | ||
---|---|---|---|
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 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., " | * 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 (Logical) | + | 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 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. | ||
+ | |||
+ | |||
+ | ===== Files ===== | ||
{{: | {{: | ||
- | {{: | + | {{: |
+ | |||
+ | {{: | ||
webteam/webplan/2011/section6_recommendations.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1