Headlights2013/SiteRedesign
From W3C Wiki
(Difference between revisions)
(→Participants) |
|||
| Line 42: | Line 42: | ||
* July: W3C management evaluates proposal and determines what resources to allocate. | * July: W3C management evaluates proposal and determines what resources to allocate. | ||
</ul> | </ul> | ||
| + | |||
| + | == Topics == | ||
| + | |||
| + | <ul class="show_items"> | ||
| + | * Audit (number of pages, top hits, sections of site, ...) | ||
| + | * Analytics (check with Wendy and Ted on status of policy work) | ||
| + | </ul> | ||
| + | |||
== Random comments == | == Random comments == | ||
Revision as of 14:57, 27 February 2013
This public wiki holds notes related to the 2013 Headlights task force on redesigning the W3C site. Questions? Contact Ian Jacobs <ij@w3.org>.
Contents |
Participants
- Ian Jacobs, W3C, Chair
- Robin Ginn, Microsoft
- Sorin Stefan
- Troy Allison, Intel
- Michael Nieling, Ocupop
- Ted Guild, W3C
- Bev Corwin, The Information Architecture Institute
- Doug Schepers, W3C
Anticipated activities
- Identify primary audiences and determine priority needs (through interviews, surveys, etc.).
- Examine current subsites (public, member, group home pages, mailing list archives) and establish a scope for the project.
- Enumerate site requirements (e.g., on use of standards, accessibility, mobile versions, use of tools).
- Examine content creation and maintenance at W3C (e.g., w3c blog, news from groups)
- Study possible infrastructure solutions (e.g., off the shelf open source CRM versus rolling our own; integration with other W3C infrastructure)
- Establish a timeline and budget for implementing the plan by Q4 2014.
Deliverables
- The primary deliverable of this project will be the results of our study, a proposed redesign scope, budget, and timeline.
- We may work on information architecture, wireframes, and other artifacts to help us work with users and discuss the project.
- We may also look for funding.
Timeline
- February: Formal "launch date"
- February - June: Develop ideas
- 9-11 June: W3C discusses at its annual Membership meeting
- June - July: Further refinement
- July: W3C management evaluates proposal and determines what resources to allocate.
Topics
- Audit (number of pages, top hits, sections of site, ...)
- Analytics (check with Wendy and Ted on status of policy work)
Random comments
- Mailing list archive redesign
- StratML in charters (via Phil)
- Improve readability of font
