Plan for getting core WPD content sorted out

Hi all,

I was just thinking about this. I've seen some discussion going back and forth about adding documentation to WPD for stuff like Audio API and CSS regions. That's great, but surely we should concentrate more for a bit now on getting some of the existing HTML/CSS/JavaScript core stuff sorted out? Getting that core stuff in place is surely a higher priority than documenting nascent standards features that currently have limited browser support. I am happy to work with Julee and the others to formulate a plan for this.

After I've got the high level page structures/IA/UX in a bit more working order over the next couple of weeks, I am happy to start contributing to the low level content myself.

I'd say a general plan would be:

* Split the content into areas of responsibility, e.g. CSS learning articles (concepts plus tutorials), CSS property references, CSS selector references, HTML learning articles, HTML element references, etc.
* Assign those areas to individuals who can take responsibility for their tending
* Get people working on those areas over the next couple of months. I'd say each domain area needs an editor and a proof reader, possibly a demo writer as well, as when Lea gets Dabblet in place, we'll need to install live demos on all the articles.

Shall we discuss this at the general meeting on Monday?

Chris Mills
Open standards evangelist and editor, Opera Software
Co-chair, web education community group, W3C
Author of "Practical CSS3: Develop and Design" (

* Try Opera:
* Learn about the latest open standards technologies and techniques:
* Contribute to web education:

Received on Saturday, 1 December 2012 10:33:30 UTC