Re: List of TODOs discovered during the QA Review

  1.  +1
  2.  +1
  3.  Test pages have been needed in the past to test imports and such.
  4.  Web Platform Wednesdays and some guidelines are also in Meta, so a review would be good.

Also, a lot of the pages I checked have a section called “Related Pages (MSDN)”,[1] indicating imports that haven’t been resolved.


Julee Burdekin
Content Strategist
Adobe Web Platform

From: Amelia Bellamy-Royds <<>>
Date: Friday, July 4, 2014 at 5:39 PM
To: WebPlatform Public List <<>>, Doug Schepers <<>>
Subject: List of TODOs discovered during the QA Review
Resent-From: WebPlatform Public List <<>>
Resent-Date: Friday, July 4, 2014 at 5:39 PM

Hello all,

I've been having various chats by email and IRC about quirks and questionable content discovered while assigning readiness states during the QA Sprint.  RenoirB suggested that I start an email thread to collect them all -- and suggestions on what to do with them -- in advance of the next community telcon.

Here's what I have so far.  Please reply with any additions to this list or related commentary.

1. Glossary pages.  There are a number of pages in the top-level file path (like wiki/absolute_unit) that contain glossary entries.  These should all be grouped into a logical file path like wiki/glossary/absolute_unit, but there are probably other things that can be done to make the glossary as a whole more useful and organized.

2. Tables with listings of other pages.  We've discussed the problems with the formatting and content of listings in a separate thread [1], but this should move up the priority once the QASprint is over.  [1]:

3.  TEST: namespace pages.  With a completely separate test wiki, I don't think there is any use for the TEST: namespace, but the pages should be reviewed to determine if there is content that should be merged into the main wiki before they are deleted.

4.  Similarly, renoirB noted that there is a Meta: namespace which was used to back-up custom content before mass import of docs from MSDN.  These need to be reviewed and content merged into the main docs (perhaps this could be a DocSprints task?).

5.  Imported pages with no page templates / default forms.  There are a lot in the SVG pages I was going through, but there may be others.

Any other quirky issues to add to this list?  Of course, you will have also discovered a lot of content-related TO-DOs, to address all the "Not Ready" and "In Progress" pages.  But for now, I'm mostly focusing on issues where a decision has to be made about what should be done.

Amelia BR

Received on Thursday, 17 July 2014 21:30:39 UTC