I've done some more on the TODO list that Curtis pointed out (below). I've been working on http://www.gnome.org/start/2.0/ as an example of old content that needs fixing for validation and flagging as out-of-date(?) content. For flagging the content I propose an additional 'warning' id in the default.css like so: ftp://ftp.dakota.net.nz/pub/default.css-jack_stewart-add_warning_id.patch then on pages that need to be flagged for out-dated content or otherwise add a <div id="warning"> with a <h3> and <p> explaining the warning. Here's an example of it in action: http://www.dakota.net.nz/jack/gnome/warning.html Comments? I've updated the /start/2.0/ section so it validates, is utf8 and converted it to the wml format (so it integrates and updates when we change headers etc in the future) and also so it includes the above warning div on each page. However, this has involved removing and adding (renaming) files and, since I don't have cvs access, I cannot create a diff of this work. So what I have done is create a package with all the modified files in it. Hopefully someone can grab these and put them in their own checked out copy and review them: ftp://ftp.dakota.net.nz/pub/gnomeweb-wml-jack_stewart-start_2.0_validate.tar.gz -- Jack > Easy fixes > 1. *.g.o sites (www, developer, foundation, etc) should > reference their own content using relative-from-root > URLs ('/arch/lang/'). Most of the pages have absolute > URLs, which makes link testing awkward from your > localhost. > 2. Pages must be valid XHTML transitional at the least. A > lot of pages are not. Many pages were generated using > tools that could not even make valid HTML 2.0. This is a > huge, and somewhat monotonous task, but an important one > that many people of varying skill can make a > contribution. I did a find on the html in d.g.o and ran > tidy (tidy.sf.net) to make this report of errors and > warning. > http://members.cox.net/sinzui/validation-report.log > I like tidy because once you have addressed the > major errors, it can clean up the small errors in markup > and even convert formating tags and attributes into > styles. > 3. Convert iso-latin-1 to UTF-8. This is an awkward task. I > cannot recommend a perfect tool. Tidy will output UTF-8 > if you set the flag to convert the page to XHTML, but I > have had some problems with that. I have used > native2ascii that ship with Java, and while it dutifully > converts content, it will not change any character set > declarations in the page. > 4. Flag abandoned and depreciated pages and documentation. > We don't have a policy for this. I don't think we should > be contributing to dead links be removing these pages. > Instead, we need to update them to indicate they are > abandoned or depreciated, and remove all site links to > them. We may want to provide an index to old documents > that might have some historical value.
Attachment:
signature.asc
Description: This is a digitally signed message part