Published in Web Development on Wednesday, July 21st, 2004
Everyone's talking about it, here's one persons interpretation of how to use Headings.
It seems to be a hot topic these days. I wrote about my views in March, and they haven't changed, however I think I can explain them better, and have a better understanding of how I feel.
Notice how many times "I" is used in that first paragraph. Make no mistake, this isn't a straight forward topic, it can be personal, and there are many interpretations. I present my thoughts here in the hopes of hearing what others may think of them.
Below are the posts that fanned this fire ;-]
The first post in that list started this examination of headings by looking at blog markup.
Anne van Kesteren makes a good point, saying that
This is fine. If one assumes that each individual web page is a document, then we could assume that the components that make up that document are, in fact, legitimate pieces of that document.
The specs state the following:
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.
There are six levels of headings in HTML with H1 as the most important and H6 as the least. Visual browsers usually render more important headings in larger fonts than less important ones.
Noting that this is in the 'global structure of an html page', we can see that laying out the headings, with each describing the
topic of the section it introduces, those headings
may be used by user agents, for example, to construct a table of contents for a document automatically.
The second paragraph indicates the hierarchy of the headings relative to each other.
The result of the above is pretty much what Tomas was saying in his article (I think!). Personally, I believe that each document has one purpose or objective, and therefore, one <h1>:
While I do agree that we are bending the tools a bit to fit our needs, the method presented above, for me, gets the job done ;-] (until someone uses the comments to poke holes in the theory!).
I started freelancing by diving in head first and getting on with it. Many years and a lot of experience later I was still able to take away some gems from this book, and there are plenty I wish I had thought of beforehand. If you are new to freelancing and have a lot of questions (or maybe don't know what questions to ask!) do yourself a favor and at least check out the sample chapters.
Like the other books listed here, this provides a great reference for the PHP developer looking to have the right answers from the right people at their fingertips. I tend to pull this off the shelf when I need to delve into new territory and usually find a workable solution to keep development moving. This only needs to happen once and you recoup the price of the book in time saved from having to develop the solution or find the right pattern for getting the job done..