I'd go for nested lists
ul
liheading 1
ul
liitem 1/li
...
/ul
/li
liheading 2
ul
etc...
And use h's where they are actual headings like Dave Woods suggested.
Gr.
Matijs
On Wed, Apr 9, 2008 at 4:58 PM, Joseph Ortenzi [EMAIL
That makes good sense Matijs but it would take some work to get my cms
to do that.
Maybe a dl would be the best comprimise?
Is there a huge difference between using that structure and a definition
list?
-thanks
kevin
Matijs wrote:
I'd go for nested lists
ul
liheading 1
ul
but it makes sense to make sense! ;-)
worth the effort
On Apr 14, 2008, at 10:17, kevin mcmonagle wrote:
That makes good sense Matijs but it would take some work to get my
cms to do that.
Maybe a dl would be the best comprimise?
Is there a huge difference between using that structure
Go for the first option...
h2section title/h2
ul
liapage name 1/a/li
liapage name 2/a/li
...
/ul
Google won't give anymore weight as it'll simply dilute the weight of all
your h3 tags so only use them where they're relavant and where they are
actually heading up contnet.
I'd always advise
Hi,
I'd say use a list, for two reasons. Firstly you said im generating a
stronglist/strong of page links, and secondly a heading should be a
heading for something that comes after it in the content. So not this:
h3apage name/a/h3
!-- something should be here... --
h3apage name2/a/h3
But this
list
On Apr 09, 2008, at 14:36, kevin mcmonagle wrote:
hi,
im generating a list of page links from my cms, its not really for a
nav bar just a section of the site that has a number of related
articles.
im using h2 for the over all list label but am wondering what to
use for the list
