Hello Everyone (Assuming anyone beyond me and Micheal are sub'd to
websites at pwg.org)
I've volunteered to develop the new pwg website. I've chatted a bit
with Micheal over private email but I'll try to do most things in the
open over this mailing list.
October sounds like a good timeline, I know I hope to have everything
implemented before then but I know enough not to trust my estimation
skills.
Goals 0-3 look good. I was thinking on the generalized user
experience. I do not expect the self-certification and IPP-Everywhere
badge will be ready before the site launches but I want to include
those sections in the implementation. We can then comment them out
until the program goes live.
With the certification and badging I think we introduce a total of
three distinct users for pwg.org:
1. Consumers
2. Implementers
3. Collaborators (Workgroup members)
I want to segragate these group's sections. So consumers will be
guided to the IPP Everywhere end user pages where we talk about IPP-E
in terms of features. This would be the section where the IPP-E
printer list would help. Implementers would be shown final released
versions of standards and guided to register their printer or
implementation. Best practice white papers and pointers to licensable
implementations would also encourage adoption.
Collaborators is where automation should help the everyday running of
the PWG. Calendars, surveys, host space for drafts. Anything where you
thought "This is annoying. Why do I have to do X?".
On a personal level I want to go overkill on the consumer and
implementer sections. I think that if only we implemented it enough
and marketed it enough IPP-E could "solve" printing and unlock uses
we've never seen printing handle before. I know I've mentioned this to
Ira and Glen before and they were more realistic, still I want to
contribute to the impossible dream where I can.
I have included my website ideas into a prototype homepage which I
hope to hosted tomorrow. Flying home I wrote a tiny vision document
also dealing with the user segregation, my ideas here are summaries of
that document. Said document should go up with the website.
Implementation details wise I would suggest wordpress. By default it
covers our more dificult needs like change history, roll-back, and
more features than I could ever hope to implement. The plugin
ecosystem can provide the missing features like surveys and
moderation. It is not without downsides, wordpress is activly
maintained so we'll have to need it upto date else get the website
defaced. I also have some experience with social integration. On the
whole I would suggest against it for the pwg. It is a good idea to
market the consumer pages, how I am not so sure on.
Daniel
2013/7/31 Michael Sweet <michael.r.sweet at gmail.com>:
> 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.
>> 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
>> _______________________________________________
> Website mailing list
>Website at pwg.org>https://www.pwg.org/mailman/listinfo/website