On 01/10/2010 15:22, Thierry Koblentz wrote:
Hi Tee,

I thought this is suffice but then I am not sure as these HTML5 tags
are still too new for me.

  <section id="articles">

       <article>
<h2>...</h2>
<p>...</p>
     </article>


       <article>
<h2>...</h2>
<p>...</p>
     </article>

  </section>

What about something like this?

<ol id="articles">
   <li>
     <article>
       <header>
         <h1><a href="#">Article Title</a></h1>
       </header>
       <p>Lorem ipsum dolor sit amet, ...</p>
     </article>
   </li>
   <li>
     <article>
       <header>
         <h1><a href="#">Article Title</a></h1>
       </header>
       <p>giat nulla pariatur. Excepteur sint occaecat cupidatat
       non proident, sunt in culpa qui officia deserunt mollit anim id est
       laborum.</p>
     </article>
   </li>
</ol>

let's not get into list-itis again... ;)

to answer the thread starter: there will probably be no clear single answer about what is and isn't "too much semantic markup". it will come down to your own personal preference, i'd say...whatever you feel comfortable with (particularly as currently there's no practical benefit of using these new structural constructs - e.g. there's no crawlers looking specifically for <article>s to syndicate etc).

P
--
Patrick H. Lauke
______________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
______________________________________________________________
twitter: @patrick_h_lauke | skype: patrick_h_lauke
______________________________________________________________


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************

Reply via email to