Hi all, Soon I'll have a bit about the recent findings from our various outreach efforts at the last two doc sprints (surveys, verbatims, observations), and in that I'll summarize the findings and suggest some KPIs and goals around getting started and usability. We can then build workflows and monitor them to track results via Patricks on-page analytics and flow analysis. I fully support Doug's idea of stubbing out the wiki and thereby eliminating the page creation step. However, we should not count on being able to do this right away. We still need to settle on a taxonomy for the DOM pages and so forth. +Scott On Tue, Mar 5, 2013 at 5:03 AM, Doug May <intuedge@gmail.com> wrote: > Hi, Julee. > > I definitely vote for stubbing in the missing pages, with a clear > caveat about missing info, an indication of relative priority, an > invitation/links to contribute (getting started and checkout), and > ideally a way to vote the priority up or down. > > I missed most of Friday's call. Is there a place to locate the > recording, or the IRC capture? > > DougM > intuedge@gmail.com > > > > 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 16:47:28 UTC