On 10/18/06 4:04 PM, "Mike Schinkel" <[EMAIL PROTECTED]> wrote:
> My point was simply to be careful not to overwhelm the user with text on a > intro page as it has been proven people scan web pages instead of reading > them[1]. Less will be more here. Justin presents this[2] as an example, but > I find it to be far too much information on an intro page. This is a general > principle, of course, not true in all cases but likely true for an intro > page. Os I would highly suggest that whoever is involved in creating intro > pages first read this[1]; it was eye opening when I first read it. This is an excellent point Mike, and one I strongly agree with. I have taken it to heart and will seek to simplify/reduce the text on intro type pages as much as possible without losing meaning/utility. > Again I agree. I think specs are *the most important thing* to one class of > people, i.e. those specifying the spec. That's actually not true. The spec is the most important thing to people *implementing* the spec. Implementers need to be able to read very precise descriptions of what they are implementing in order to maximize the chances of them implementing it correctly and interoperably. > As such it's no surprise that the > spec gets primary focus, at least initially. But it needs to be balanced > because there are many classes of people and for each of them there is > potentially a different "most important thing." So it needs to all be > easily accessible and findable understanding how users read web pages[1]. Strongly agreed. Thanks for this feedback Mike - you make very good points. Tantek _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
