Re: DOM reorg project next steps

Thank you very much!

In October, 2012 until January, 2013 (I think), I started the clean up
journey but did not get too far. I did not want to make substantial moves
before consulting (and without a proper script, since doing this manually
can take many, many hours, including fixing the links to the moved pages).
I did clean up the content for a lot of pages (and created a
"proprietary"<http://docs.webplatform.org/wiki/dom/proprietary>path as
a sink for Internet Explorer specific content and perhaps even
moved a few over there, which is halfway to deletion), though, but I
eventually put less and less effort in it and ended up semi abandoning it
(I always plan to return, though! ;)). The great discouragements I had were
the inconvenient templates, the "applies_to" field below, the currently
inconsistent (within itself, and when compared to the rest of the content)
hierarchy, the lack of automatic heritage for subclasses and the
uncertainty of the future of the (manual) compatibility tables.

We have an issue regarding the applies_to field - it cannot be populated
with multiple objects. For example, the name attribute/property is only
specified in HTML5 for certain properties and instead of creating a "name"
article for every HTML element object, it would be much more convenient to
define a list of relevant objects to which it applied (unless we have
another way of doing it).


☆*PhistucK*


On Wed, Dec 4, 2013 at 10:36 PM, David Gash <dgash@google.com> wrote:

> Hi all,
>
> As you may know, one of the big projects on my Google contract is
> reorganizing the pages under docs.webplatform.org/wiki/dom, as outlined
> in Scott Rowe's project document<http://docs.webplatform.org/wiki/WPD:Projects/DOM_API_docs>.
> Most of these pages were imported and many ended up miscategorized or
> placed under unneccessary interstitials, so I'm moving them about and
> correcting the "applies_to" fields in a concentrated effort to end up with
> a more straightforward, logical URL structure.
>
> I am *not* editing page content during this project, the goal being to
> first get the pages where they belong, so that they can easily be found for
> later updating.
>
> I've been working on this project for several weeks, and have completed
> the dom/apis/audio-video, dom/events, and dom/objects branches; this leaves
> dom/apis, dom/properties, and dom/methods. There are just over 600 pages in
> that set, each of which must be examined and either edited & moved or
> deleted. That's my next group to work on.
>
> Peter Lubbers has asked me to post this to the list before I begin this
> group, to make sure that no one else is working on those pages and that no
> one has objections to the plan. If yes to either, please let us know.
>
> Thanks,
> Dave Gash
>
>