Unfinished writing, and header elements Feb16 '05
Although the big news yesterday was IE 7, I’d like to mention header elements, and my source for such an inspiration.
First off, I usually expect a little more from Andy Budd – he leaves his article so open, that I’m not sure what to think, or how to proceed, to make things better.
He doesn’t show any examples of how web authors are doing things wrong, nor does he explain how to correct the problem, or misconception.
This is not good writing.
Header elements
Header elements (<h1>, <h2>, etc.) exist for the sole purpose of briefly describing a section of a web site – anything really – text, photos, etc.
The problem that Andy has stated is that web authors tend to use header elements for the wrong reason. That reason (I am still trying to figure out) is when web authors use header elements as a "navigation notifier," that tells you each page that you are on – sort of like "chapters in a book."
Now... I still don’t fully understand what he means, so bear with me, as I try to vaguely explain his reasoning.
My thoughts
I tend to only use <h1> for the main site title, in this case "matthom." I understand that more than one <h1> can be used per page, but why bother, when I can just go to <h2> for my next level headings, which would be my blog entry titles.
See, this is where I am assuming I am wrong – yet I have no idea how to fix it.
<h1> elements should be used whenever there is a section that needs a brief intro, and as my article (or section) gets more involved, I should start using <h2>, <h3>, etc – to break things down even further. THIS... I believe, is somewhat more of a proper way to utilize header elements.
Write headers last
My method of writing headers is to write them last. In other words, I write (or input) the content first, and then go back and create headers (if need be).
This is almost similar to writing a term paper. Your thesis is like a header element. It contains some pretty important information about the section that follows.
But... do you write your thesis first, or last? I usually prefer to spill my thoughts, and then finalize things with a thesis – after I have a clear picture of the entire paper.
The same goes for writing content on a web page. If I don’t write the content first, then I have barely a vague idea of what the header will be.
On blogs
Although I pick on Andy Budd for his entry (or lack of entry), he has done nothing wrong, except leave readers slightly befuddled.
Typically, with blogs, there are no rules on how entries should "complete themselves." In my opinion, I tend to (at least) leave readers in a state of "understanding." I also like to give some direction, as much as I know, to other resources, etc.
Categories: Markup 
, People , Semantics
Add Feedback (view all)
Leave feedback
is published and produced by Matt Thommes - an independent publishing enthusiast, mobile blogger, content creator, informative writer, web developer from Chicago.
Never one to conform, Matt intends to promote the effect the web has on our lives, in an effort to intensify, instruct, and clarify all that is happening around us.
Similar Entries
- Forget a new site or CMS, just jump right in and start writing (43 recent visits)
- Watch the double negatives when writing (2 recent visits)
- No distinction between blogging and writing (1 recent visits)
- Writing a music blog (0 recent visits)
- Best practices for writing on the web (2 recent visits)
Stats
2 unique visits since August 2008