Re: PHP Manual problems
| From: | Robert Cummings | Date: | Wed, 10 Feb 2010 19:05:59 +0000 |
| Subject: | Re: PHP Manual problems | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-301955@lists.php.net to get a copy of this message | ||
Michael A. Peters wrote:
Robert Cummings wrote:Many government documents have the concept of "aside" as appearing through the document and contextually near to the information to which the aside relates. The entire sidebar seems a bit gratuitous as an "aside". Sure it's aside, but it's not exactly the semantic meaning of aside. From the W3C Working Draft:Just a word of thought... if you're doing styling... use classes and not IDs. Use of IDs for styling is very often indicative of inexperience, inability, or lack of understanding with respect to CSS.I use ID when there will only be one element that needs to be styled that way. Whether it implies a lack of understanding or not, I don't care about. It's not incorrect and if you are doing a fixed width layout where the aside (sidebar) is positioned on the page by the style sheet (allowing your content to be the very first thing in the page source), you only want one element attached to it anyway. For the wrapper divs around article and section I do use class because there may be more than one article on a page (though usually not) and there almost certainly are multiple sections within an article.
"The aside element represents a section of a page that consists
of content that is tangentially related to the content around
the aside element, and which could be considered separate from
that content. Such sections are often represented as sidebars
in printed typography.
The element can also be used for typographical effects like pull
quotes."
http://www.w3.org/TR/html5/semantics.html#the-aside-elementCheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP