[pwg.org] Goals and requirements for the pwg.org site redesign

[pwg.org] Goals and requirements for the pwg.org site redesign

Michael Sweet michael.r.sweet at gmail.com
Thu Aug 1 11:51:50 UTC 2013


And I forgot one (added to the end below)

On 2013-07-31, at 12:42 PM, Michael Sweet <michael.r.sweet at gmail.com> wrote:

> All,
> 
> Now that we have the new server up-and-running, we can start work on the new web site. I have setup a beta test web site on the server for this work, available at:
> 
>     http://beta.pwg.org/
> 
> The goals and requirements of the new site are (roughly in order of importance:
> 
> 0. Adopt the new PWG logo and colors.
> 
> 1. Allow PWG members to add and update pages to the web site without hand-editing HTML files and using FTP to upload those changes to the site directory.
> 
>    - This probably means using some sort of Content Management System (CMS)
>    - Ideally we want a change history of pages in case errors are made and we need to roll back a change.
>    - We don't want this to just be a Wiki as we've been down that road before and the consensus is that they don't work well for our membership.
>    - New pages need to be moderated by the PWG Webmaster.
> 
> 2. Allow PWG members and our marketing folks to post articles to the home page (i.e. a Blog) that are of general interest to the membership and industry we represent.
> 
>    - New articles need to be moderated by the PWG Webmaster.
>    - The ability to post comments to articles would be nice (again, with moderation).
> 
> 3. Provide survey pages for meetings and articles.  Right now we use Survey Monkey.
> 
>    - Meeting surveys ask for name, organization, and the days that will be attended (in person, call in, or not attending)
>    - Article surveys could be as simple as rating the article and providing plain text comments.
>    - We'd need both the "take the survey" page and a page showing a summary and details of all responses.
>    - Nice to have: arbitrary surveys with multiple choice questions, CSV export of responses, graphs, etc.
> 
> 4. Provide a registration page for IPP Everywhere implementations.  This will be used to support IPP Everywhere self-certification.

4.5. Provide an issue tracking page for errata and registration issues

> 5. Provide integration with LinkedIn, Facebook, Twitter, and other social web sites.
> 
>    - "Tweet" (Twitter) or post (LinkedIn) new articles as they are published
>    - "Like" new articles or pages (Facebook)
> 
> The timeframe for items 0-3 to be rolled out should be by the October 22-24, 2013 F2F meeting in Cupertino, CA.
> 
> Thoughts?
> 
> _____________
> Michael Sweet
> 

_____________
Michael Sweet



More information about the Website mailing list