Difference between revisions of "Headlights2013/SiteRedesign"

From W3C Wiki
Jump to: navigation, search
Line 37: Line 37:
* Timeline for implementing the proposal by end of 2014
* Timeline for implementing the proposal by end of 2014
=== Phase II ===
== W3C Audiences ==
== W3C Audiences ==

Revision as of 20:44, 25 March 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>.

Thanks to the participants for their work! Discussions on public-site-design@w3.org (archive)


    • Identify W3C audiences and their priority needs
    • Catalog key resources available on w3.org
      • What we have (e.g., specifications, blog posts, etc.)
      • What we don't have and want
      • What we expect to live elsewhere (e.g., Web Platform Docs)
    • Ensure the W3C Web site:
      • Addresses primary needs
      • Makes it easy for different audiences to find key resources
      • Communicates the W3C brand proposition (cf related task force)
      • Motivates people to participate and helps fuel activity.


    • Phase I: Create a proposal
    • Phase II: Implement the new site (and any processes)

Phase I

This task force will write a proposal expected to include:

    • Findings regarding key audiences and their requirements
    • High-level vision for W3C site
    • Guidance on content strategy
    • Budget estimate for implementing the proposal.
      • We might list some potential sponsors for the project.
    • Timeline for implementing the proposal by end of 2014

Phase II

W3C Audiences




  • Owner: W3C Marcomm
  • Frequency: Several weekly
  • Audience: Primarily technical


  • Owner: W3C Marcomm
  • Frequency: 5-10 monthly
  • Audience: Diverse


    • Talks
    • Meetings
    • Supported Conferences


    • Index (/TR)
    • Specifications themselves
    • Status pages

Mailing lists

Group subsites


Member subsite

Miscellaneous pages about W3C


    • Strong W3C brand story
    • Clear presentation of W3C products, and how to get involved
    • Landing pages for verticals (e.g., auto, digital publishing)


    • Web Platform Docs


    • Gather some data (with permission) for a couple of months

Notes on Implementation Requirements

    • Use of standards
    • Typography (especially for specs)?
    • WCAG 2.0
    • Mobile-friendly
    • Analytics? (may require privacy policy change)

Notes from 2008 Redesign Experience

    • We wrote our own content management system. I don't recommend that
    we do that again.