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/04/21 14:41] – aatre | webteam:webplan:2011:section6_recommendations [2011/09/07 18:09] – added more feature recos to list 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 32: | Line 32: | ||
In order to form an inclusive and diverse community welcoming all, we are recommending the creation of a formal Accessibility Advocate role, possibly as an adjunct to or within the Website Team. This role would strive to ensure that no groups of people are inadvertently barred from participating in the Evergreen community due to any reason such as visual, auditory, or motor skill impairment, language barriers, etc. We also recommend the creation of a similar role to actively participate in Evergreen software development features related to user experience. | In order to form an inclusive and diverse community welcoming all, we are recommending the creation of a formal Accessibility Advocate role, possibly as an adjunct to or within the Website Team. This role would strive to ensure that no groups of people are inadvertently barred from participating in the Evergreen community due to any reason such as visual, auditory, or motor skill impairment, language barriers, etc. We also recommend the creation of a similar role to actively participate in Evergreen software development features related to user experience. | ||
- | ===== 2. Technical | + | ===== 2. Website Recommendations |
+ | |||
+ | ==== A. Implementation of a Community Website Platform ==== | ||
+ | |||
+ | The Web Team's primary technical recommendation is to replace the existing website with an integrated community website platform constructed using existing open source software and tools. | ||
+ | |||
+ | **1. Provide a content management system that encourages content contribution from the community while allowing strong editorial management** | ||
+ | |||
+ | 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, while deprecated information is archived or removed. | ||
+ | |||
+ | **2. Provide collaboration tools that allow community members to work together** | ||
+ | |||
+ | Like most communities, | ||
+ | |||
+ | **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. | ||
+ | |||
+ | * 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 | ||
+ | * 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. | ||
+ | |||
+ | === Plan for implementing a new community website platform === | ||
+ | |||
+ | 1. Define project management team membership, responsibilities, | ||
+ | |||
+ | 2. Select a community website platform. | ||
+ | |||
+ | 3. Define and prepare website development and production environments | ||
+ | |||
+ | 4. Develop community website platform | ||
+ | |||
+ | a. Develop information architecture | ||
+ | b. Populate content as defined by information architecture, | ||
+ | c. Implement custom community and collaboration functionality using existing tools where possible | ||
+ | d. Implement a design theme that maximizes website user experience given the defined information architecture and functionality features | ||
+ | e. Implement stakeholder and community review process of completed website platform | ||
+ | |||
+ | 5. Launch community website platform | ||
+ | |||
+ | a. declare new content freeze and user account freeze on existing website | ||
+ | b. ensure content is synchronized on existing and new websites | ||
+ | c. launch new website, archiving existing website into a web-accessible archive indefinitely for future reference | ||
+ | d. begin community outreach activities to encourage membership and participation in new online community platform | ||
+ | |||
+ | ==== B. Integrate off-site sites and features into new community website platform where appropriate ==== | ||
+ | |||
+ | Benefits of centralization: | ||
+ | |||
+ | * 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 | ||
+ | |||
+ | **1. RSCEL (Resource Sharing Cooperative of Evergreen Libraries - rscel.evergreen-ils.org)** | ||
+ | |||
+ | Much of the content and functionality of the RSCEL site is aligned with the strategic goals and requirements defined during this process. | ||
+ | |||
+ | **2. Docs (Official documentation DocBook site maintained by DIG - docs.evergreen-ils.org; | ||
+ | |||
+ | Currently, documentation is contributed via the git software version control tool to enforce version control; this method is not accessible for many non-developers and represents a barrier to widespread contribution. There are many solutions for content management that provide version control in a more user-friendly manner. | ||
+ | |||
+ | **3. Community News Aggregator (Maintained by community member - planet.evergreen-ils.org)** | ||
+ | |||
+ | As the Evergreen ecosystem continues to grow, relevant content will increasingly be found off-site. | ||
+ | |||
+ | ==== 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, | ||
+ | |||
+ | * implement a categorization (" | ||
+ | * manually review as much content as possible and tag with audience tag(s) | ||
+ | * provide browsing interface allowing users to view all resources with a specific audience tag | ||
+ | * provide search interface field restricting searches to resources with a specific audience tag | ||
+ | * create curated content collections (e.g., " | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | * implement a categorization (" | ||
+ | * manually review as much content as possible and tag with topic tag(s) | ||
+ | * provide browsing interface allowing users to view all resources with a specific topic tag | ||
+ | * provide search interface field restricting searches to resources with a specific topic tag | ||
+ | * create curated content collections (e.g., " | ||
+ | |||
+ | ==== E. Implement an up-to-date list of Evergreen features that is searchable, sortable, and categorized. ==== | ||
+ | |||
+ | 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:// | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | ==== 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.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1