[UPHPU] "design standardization" thoughts

[cole at colejoplin.com]

Quoting "Daniel C." <dcrookston at gmail.com>:

> I've been thinking about "design standardization" for a while now.
> The basic idea is to create a set of definitions for different
> elements and IDs, such that developers can mark up their pages using
> the standard and then put any design that obeys the standard on top of
> their markup. Some examples of what might go into the standard:
>
>    * h1 is used at the beginning of a distinct block of content. An
> h1 always denotes the beginning of a new distinct block.
>    * h4 is used within a distinct block of content, and does not
> denote the start or end of a distinct block.
>    * The #submenu ID identifies a secondary navigation block, which
> may or may not be present on any given page. It should only be applied
> to a ul or ol.
>    * The .quote class represents a pullout quote, and should always
> be within a p tag that's inside of the #content div.
>    * Any p within the #content ID should be considered as primary site
> content.

Nice idea, but I couldn't use it as described. I have very specific  
reasons for using an H1 or H2, which has everything to do with SEO. I  
need sections descriptions, subs, just like an outline. This is the  
purpose of the HTML tag. The same goes for classes versus ids in CSS,  
they have a specific purpose. Having standardized class names and id  
names would make more sense to me as a place for programmer standards,  
IMO.

-- Cole