Maybe it's me but I think most (even W3C) HTML/CSS/Java...err..ECMAscript documentation sucks. It's very difficult to search and oh brother is it dryer than white toast that's been sitting on the counter for a few days. Recently I've been turned on to firefox's html validator. I think that's the direction you need to go ... show me documentation when I need it, where I need it and only about what I need -- I really don't want to see your *marketing pop* when all I need to know is if a tag or attribute is deprecated for a particular doctype. But hey ... that's just me.

-derby

In reply to Re: OT: Improving IE7 SDK Docs (was Let's suppose...) by derby
in thread OT: Improving IE7 SDK Docs (was Let's suppose...) by footpad

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.