Date: Thu, 1 Feb 96 12:48 CST To: firstname.lastname@example.org, email@example.com Newsgroups: comp.infosystems.www.authoring.misc,alt.hypertext,alt.culture.www Subject: WWW-RANT: Biting the hand that gave us birth-- sorry TBL Summary: critique of Tim Berners-Lee's style guide From: firstname.lastname@example.org (HyperTerrorist) Organization: The Responsible Party I've been reluctant to critique Tim Berners-Lee's WWWeb style guide at <>, because Tim invented the WWWeb, and for that alone he should bask in glory, all his days... But, all the same, his guide is seriously flawed, both in the design strategies it recommends, and the ones it embodies. So here's a brief list of what I see as its errors. Far too often, Tim fails to take his own advice: - Site not checked with lynx, navigation buttons lack ALT text thruout - Multiple audiences mixed-- beginner and technical-- tech terms undefined <Introduction.html> &c - Spellcheck needed thruout - Broken HTML <Testing.html> "client list" - Links not carefully tested - Back button skips one file <ReaderStructure.html> - Next button skips several files <ReaderStructure.html> - File revised and relocated, but many links not updated!?! <../../Provider/Etiquette.html> old <Etiquette.html> new - Inconsistent navigation buttons (so prevalent it seems intentional?) - A rare case of all buttons correctly in place <Trees.html> - Button missing from all pages but one <TITLE.html> "markup" - [Prior] button at bottom not top of page-- thruout - No [Prior] button <Etiquette.html> <IntoContext.html> - No [Next] button ('stairmaster fallacy') <../../Provider/Etiquette.html> <ReferOrCopy.html> <NoMechanics.html> - Orphan page (no up-link) <../../Provider/Etiquette.html> <../../DesignIssues/Navigation.html> - Foster-orphan (uplink skips levels) <ReaderStructure.html> <DateIt.html> - Misleading links - Disguised up-links <Etiquette.html> "This Guide" <WithinDocument.html>"style guide" <IntoContext.html> &c "Part of" - Unsignalled/confusing violations of tree-structure <Introduction.html> miniToC at end <Etiquette.html> "Signing""status" <DeviceIndependent.html> "testing" <Testing.html> "make it clear" - Unclear whether link is #-link or separate doc <> all subheads in ToC - 'Junk links' to sites used as definitions of terms <> "WWW" <../../People/Berners-Lee/> many examples - Anchor text doesn't clearly explain contents of target page <Etiquette.html> "rule file" <DocSize.html> "next" <ReferOrCopy.html> hotlist at end <ReadableText.html> "I'm" (#-link) - Anchor text trimmed excessively (the more self-explanatory the better) <IntoContext.html> "WWW" could be "WWW product documentation" <Printable.html> "single page" could be "single page version of the whole thing" <Testing.html> "HTML overview" could be "the W3C HTML overview" - Live demo-links distracting <Printable.html> "device ind." - Wasted pages - Sub-ToCs waste reader's time <Structure.html> <WithinDocument.html> - Too-short pages waste readers' time <Virtual.html> <Footnote.html> - Undescriptive table of contents should *summarize* each 'chapter' <> [better than average] The advice Tim offers is often topnotch, but occasionally very doubtful: <DocSize.html> 'One page per idea' is a bad idea with non-local latencies <Footnote.html> 'Footnotes a page each' is unworkable for the same reason. Keep footnotes on the same page. <DeviceIndependent.html> 'Use <h?> headers in strict order' is too limiting. Eg, subpages at least ought to be allowed to start with <h2>. <NoMechanics.html> FTP and other non-HTTP links should be labelled so, in general. <Trees.html> Sharing the same pages between expert and novice views is not usually a real advantage. j -==--- . hypertext theory : artificial intelligence : finnegans wake . _+m"m+_"+_ lynx ¬http://www.mcs.net/~jorn/ ! Jp Jp qh qh ¬ftp://ftp.mcs.net/mcsnet.users/jorn/ O O O O ¬news:alt.music.category-freak Yb Yb dY dY ...do you ever feel your mind has started to erode? "Y_ "Y5m2Y" " no.