- From: Julee <julee@adobe.com>
- Date: Mon, 4 Mar 2013 16:50:58 -0800
- To: Doug Schepers <schepers@w3.org>
- CC: <public-webplatform@w3.org>
- Message-ID: <CD5A8172.5BB52%julee@adobe.com>
Hi, Doug and everyone: Here are some notes from a chat Doug and I had today. ===Analytics=== We want to ensure we're succeeding at promoting content. We also want to make sure we're giving everyone a sense of the activity on the site. For instance, we tried out a process for making sure new content gets promoted with pointers. Eliot commented last week that it "seemed" effective. We need to have some analytics to make sure we're effective. We have Julee, Patrick D'Souza, Scott Rowe, and Doug on the Analytics Task Force. This is a good number to start with. Let's focus the Analytics team on the following tasks: 1. Set up the project page. 2. Begin with a basic audit and clean up, including generating a site map. 3. Define basic analytics infrastructure. 4. Create a framework for reporting to the larger community, with regular blog posts about things like traffic and new content written. Doug will add Julee to piwik. ===Milestone tracking=== Garbee has done a lot of work to get the project/issue tracking up and working. Next we want to define milestones, especially milestones to Beta, and get them as projects into bug genie: For example, to get to Beta, what content do we need and what's that criteria? What technical milestones are there? We'd then break down the projects in the bug genie. For example, with caniuse, we want to map that structure to ours so we can ensure coverage. 1. Generate a site map of the current site 2. Identify what pages should be there that aren't 3. Do we want to stub in those pages so users don't have to worry about creating them -- or creating them in the wrong places? Regards. Julee ---------------------------- julee@adobe.com @adobejulee
Received on Tuesday, 5 March 2013 00:51:18 UTC