HTML and CSS Reference
Spell Check and Proofread Your Pages
Spell checking and proofreading may seem like obvious suggestions, but they bear men-
tioning given the number of pages I've seen on the Web that obviously haven't had
The process of designing a set of web pages and making them available on the Web is
like publishing a book, producing a magazine, or releasing a product. Publishing web
pages is considerably easier than publishing books, magazines, or other products, of
course, but just because the task is easy doesn't mean your product should be sloppy.
Thousands of people may be reading and exploring the content you provide. Spelling
errors and bad grammar reflect badly on you, on your work, and on the content you're
describing. It may be irritating enough that your visitors won't bother to delve any
deeper than your home page, even if the subject you're writing about is fascinating.
Proofread and spell check each of your web pages. If possible, have someone else read
them. Often other people can pick up errors that you, the writer, can't see. Even a simple
edit can greatly improve many pages and make them easier to read and navigate.
With the introduction of technologies such as style sheets and Dynamic HTML (DHTML)
, people without a sense of design have even more opportunities to create a site that
looks simply awful.
Probably the best rule of web design to follow at all times is this: Keep the design of
each page as simple as possible . Reduce the number of elements (images, headings, and
rule lines) and make sure that visitors' eyes are drawn to the most important parts of the
Keep this cardinal rule in mind as you read the next sections, which offer some other
suggestions for basic design and layout of web pages.
Use Headings as Headings
Headings tend to be rendered in larger or bolder fonts in graphical browsers. Therefore,
using a heading tag to provide some sort of warning, note, or emphasis in regular text
can be tempting (see Figure 18.8).