This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We should formulate a plan to get the existing HTML/CSS/JavaScript/SVG/other core stuff sorted out. Getting that core stuff sorted out is just as high a priority as adding new material - we need to strike a balance of course, as the new material is valuable for cultivating excitement and community engagement, and getting community kudos. 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.
Reverting this bug's platform to All, as experience happens on all platforms.
New location: http://project.webplatform.org/content/issues/23