Difference between revisions of "Headlights2013/SiteRedesign"
(→Notes on Implementation Requirements)
|Line 246:||Line 246:|
** Internal: Custom search results
** Internal: Custom search results
** External: SEO
** External: SEO
Revision as of 21:17, 18 April 2013
This public wiki holds notes related to the 2013 Headlights task force on redesigning the W3C site. See the Calendar
Questions? Contact Ian Jacobs <email@example.com>.
- 1 Goals
- 2 Deliverables
- 3 W3C Audiences
- 4 Products
- 5 Analytics and Surveys
- 6 Resources
- 7 Critical Design Questions
- 8 Notes on Implementation Requirements
- 9 Notes on Possible BizDev Ideas
- 10 Notes on content strategy
- 11 Notes on Preliminary Qualitative Brand Research
- 12 Notes from 2008 Redesign Experience
- 13 Meeting history
- 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)
- Communicates clearly the nature and impact of the Open Web Platform
- Motivates people to participate and helps fuel activity.
- Phase I: Create a proposal; see Calendar
- Phase II: Implement the new site (and any processes)
This task force will write a proposal expected to include:
- Mission/vision statement (in development in a separate task force)
- Key audiences/users and their needs (include testimonials, etc.)
- Prioritized #Goals & high-level vision for W3C site (including value proposition)
- Scope of redesign
- Implementation requirements
- Success criteria
- Estimated budget range and potential sponsors
- Anticipated timeline for launch by end of 2014
What we will want
- Work with stakeholders (marketing, business, systems, developers, etc.) to define & draft a website governance document (see website-governance.com)
- Governance document should cover: KM: Added a few things that I've seen included in an effective 'governance doc'.
- Business strategy/vision
- Systems administration (if this doesn't exist)
- Development standards
- Content strategy (creation, maintenance schedule, workflows, etc.)
- Design (style guides)
- Social media & online community
- User experience
- Information & data architecture
- Legal issues (privacy, copyright, etc.)
- Developers and designers
- C-Level audiences in diverse industries
- Members (notably Advisory Committee Representatives)
- Chairs (of all types of groups)
- Developer relations team
- Business development staff
- Web Accessibility Initiative
- Systems Team
- W3C Management ("W3M")
One view of W3C's main products:
- Standards (and supporting materials like tests)
- Venue for standards development (groups, Membership)
- Validator service
- Additional offerings for developers (webplatform.org, training, w3conf, html5 logo, ...)
Analytics and Surveys
- Gather some data (with permission) for a couple of months (Ian)
- What are top 100 visited URIs?
- What are top 25 search terms?
- Where do people use search box?
- What are the top 10 links followed from the home page?
- What are the top referrers?
- How many unique visitors?
- How do people enter into the site? (Homepage or other?)
- Where are we losing users?
- Other info that we can gather from the search bar & dashboard? (Robin)
- See Dorian Taylor on visualizing paths from apache logs
- Google webmaster tools?
- Ian can do 1-1 interviews with Members in June during AC meeting (though we will need other data by then already)
Where we might find people to respond
- Community Group participants (2500 people)
- W3C Member developer communities
- Information Architecture Institute
- IAI Partners? W3C Partners?
- W3C subsidiaries?
- W3C mailing lists?
- Owner: W3C Marcomm
- Frequency: Several weekly
- Audience: Primarily technical
- Owner: W3C Marcomm
- Frequency: 5-10 monthly
- Audience: Diverse
- Supported Conferences
- Idea: make it easier for groups to publish their own calendars and aggregate them in the site calendar.
- Index (/TR)
- Specifications themselves
- Status pages
- Clear indicators of status, done-ness
- Integration with webplatform docs and testing
- Other future services
- Should member home page be a dashboard of an individual's view of W3C?
- Do members use the home page? News page?
- Relation of news page to optimized email strategy to members (e.g., batch non-critical emails to be once weekly)
Miscellaneous pages about W3C
- Strong W3C brand story
- Clear presentation of Open Web Platform
- Clear presentation of all the ways to get evolved
- Landing pages for verticals (e.g., auto, digital publishing)
- Web Platform Docs
- Website Governance Docs:
- online strategy
- systems & software administration, hosting
- online marketing & communications
- online brand strategy, brand management, reuse, licensing, etc.
- customer service
- business development
- online community & social media
- content strategy, guidelines
- translation guidelines
- website graphic design
- user experience (analysis/design)
- information/data architecture
- website analytics
- website security guidelines
- website archiving?
- website outsourcing?
- website accessibility guidelines
- website legal issues (i.e.: copyright, DRM, trademark, privacy policies, etc.)
- website information ethics, users, user data, etc.
- website training, knowledge management, knowledge guildlines
- W3C organizational needs and objectives
- website size, metrics, performance guildelines
- website team, roles, responsibilites
- workflows, processes, models
- website multi modal strategy
- website multilingual & multimodal content strategy
- content authoring guidelines, rules, style guidelines
- pre-translation guidelines, global standards, etc.
- website localization
- geopolitical policy
- website updates, refinement policy
- API guidelines
Critical Design Questions
- Sponsor logos on the home page (links? limit to 1 year? how many ok?)
Notes on Implementation Requirements
- Move to HTML5
- Use of standards
- Typography (especially for specs)?
- WCAG 2.0
- Establish importance of content in multiple languages
- What are users currently doing with translations?
- Search strategy.
- Internal: Custom search results
- External: SEO
- User testing
Notes on Possible BizDev Ideas
- Stickiness of various items on the home page (e.g., services, sponsorships)
Notes on content strategy
- What content will be centralized (e.g., through w3t-comm)
- Getting shared vision in the community for the site's intent (for content creation over time)
- What content do we expect to centralize?
- Distributed editing (in terms of responsibility)
- Any tool that produces HTML
- Org commitment to pages / maintenance
- Templates for frequently used information (e.g., templates for workshops, meetings, minutes)
- Guidelines not rules
Notes on Preliminary Qualitative Brand Research
- "Describe W3C"
- Develops, publishes and promotes Web standards
- Does this in way that’s best for society
- Improves accessibility on the Web
- Sets the stage for the Web to evolve
- Provides interoperability, openness
- Process is based on consensus, transparency, neutrality
- Competent staff
- Open, inclusive environment
- Solid technology foundation
- Offers framework for innovation (but not all agree W3C is, or should be, innovative)
- Collective collaborative culture
- Slow, reactive
- Lack of W3C Brand awareness
- Re-evaluate W3C’s Brand Position
- Do more marketing, esp. of W3C
- Better promote W3C’s membership benefits
- Address perceived business process issues
Notes from 2008 Redesign Experience
- We wrote our own content management system. I don't recommend that