RE: [WSG] Quick h1,h2 etc question
Title: RE: [WSG] Quick h1,h2 etc question Thanks all, I thought 2 was the way to be doing it, I'm sure I'd read on the W3C though that they had to be used to structure an ordered numerical hierarchy, but I can't imagine many practical examples where you might do this. Thanks again, Jamie
Re: [WSG] Quick h1,h2 etc question
I can't see any problems with your second example in theory - but it's an impossible question to answer without content. Remember that (X)HTML elements are supposed to describe or explain (for want of better words) the content that they are marking up. So there aren't any rules as to how header tags should nest or be ordered, for it depends completely on how you've laid out your content. My 2 bob's worth, anyway! ;-) On Tue, 1 Feb 2005 12:11:57 -, Jamie Mason [EMAIL PROTECTED] wrote: Hi, I'm sure this has been asked time and time again and is probably a daft question, but which is the proper way to use header tags? Thanks in advance for your patience and help! Jamie Is it... = 1) All headers must be used in order only, so most important headers go at the top then grade downwards with less important headers always being lower down = h1/h1 h2/h2 h2/h2 h3/h3 h4/h4 h4/h4 ..etc = Or = 2) With the exception of h1 used once, can you set the headers out loosely in the same tree structure lists are set out in? So h3 would only be used as a child (but not nested within) of an h2, h4 as a child of h3 etc? Then reading downwards through the headers, you're allowed to move backwards say from an h3, back to an h2? I'm not sure how to explain my question, but basically I think, can you define tree structures with headers? or do they have to be used in an ordered numerical hierarchy? = h1/h1 h2/h2 h3/h3 h3/h3 h2/h2 h3/h3 h3/h3 h4/h4 h4/h4 h2/h2 -- Jason Foss http://www.almost-anything.com.au http://www.waterfallweb.net Windows Messenger: [EMAIL PROTECTED] North Rockhampton, Queensland, Australia ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Quick h1,h2 etc question
Jamie Mason wrote: Hi, I'm sure this has been asked time and time again and is probably a daft question, but which is the proper way to use header tags? Thanks in advance for your patience and help! Depends on what you want to optimize. Tonico ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Quick h1,h2 etc question
G'day Think of the headings as a collapsible outline, with sections and sub-sections, each with a heading of the *appropriate* level. Collapse it (as one can do in Word for instance) and you should see an outline made up of headings that makes sense. Each h2 belongs to a sub-section of the main h1. Each h3 belongs to a sub-sub-section under the h2. And so on. You can have multiple h2's each with multiple h3's etc. That means... Your second version. Regards -- Bert Doorn, Better Web Design http://www.betterwebdesign.com.au/ Fast-loading, user-friendly websites ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Quick h1,h2 etc question
Have to remember that search engines will read the contents of header tags so i think best way is for heading text, titles etc. For list headings i think it would be easier to using a seperate style. The second option i think is the better way to go though, just for organization and nice and clean and structured. Thats what i think anyway :) On 01/02/2005, at 8:11 PM, Jamie Mason wrote: Hi, I'm sure this has been asked time and time again and is probably a daft question, but which is the proper way to use header tags? Thanks in advance for your patience and help! Jamie Is it... = 1) All headers must be used in order only, so most important headers go at the top then grade downwards with less important headers always being lower down = h1>/h1> h2>/h2> h2>/h2> h3>/h3> h4>/h4> h4>/h4> ..etc = Or = 2) With the exception of h1 used once, can you set the headers out loosely in the same tree structure lists are set out in? So h3 would only be used as a child (but not nested within) of an h2, h4 as a child of h3 etc? Then reading downwards through the headers, you're allowed to move backwards say from an h3, back to an h2? I'm not sure how to explain my question, but basically I think, can you define tree structures with headers? or do they have to be used in an ordered numerical hierarchy? = h1>/h1> h2>/h2> h3>/h3> h3>/h3> h2>/h2> h3>/h3> h3>/h3> h4>/h4> h4>/h4> h2>/h2>
RE: [WSG] Quick h1,h2 etc question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lea de Groot Sent: Tuesday, February 01, 2005 7:18 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Quick h1,h2 etc question On Tue, 1 Feb 2005 12:11:57 -, Jamie Mason wrote: 2) With the exception of h1 used once, can you set the headers out loosely in the same tree structure lists are set out in? This is the way I use it. I think option 1) would be very inefficient - documents just aren't structured like that. warmly, Lea -- ** Or you could refer to the specs (mostly to restate the issue not resolve it): A heading element briefly describes the topic of the section it introduces. Heading information may be used by user agents, for example, to construct a table of contents for a document automatically. And just to interject an element of contention there is this as well: Numbered sections and references HTML does not itself cause section numbers to be generated from headings. This facility may be offered by user agents, however. Soon, style sheet languages such as CSS will allow authors to control the generation of section numbers (handy for forward references in printed documents, as in See section 7.2). Some people consider skipping heading levels to be bad practice. They accept H1 H2 H1 while they do not accept H1 H3 H1 since the heading level H2 is skipped. The discussion centers around whether or not each page should have an h1, can there be more than one h1 per page, and should skipping be tolerated? It's a fun Gordian knot. drew ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
